Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 003b5974e4c89d7ea9214cc5c58a4dc35104476431f6203241c7108f849f5ea5

Tx prefix hash: dd20a877f1f04c077ca330f3898b64cf6da8dc71f2af46e64cdc593597f2ec80
Tx public key: d514c9814611148d22baf56cf00e64693243e81081a3d7c765b2379ee26441f9
Timestamp: 1754950677 Timestamp [UCT]: 2025-08-11 22:17:57 Age [y:d:h:m:s]: 00:107:22:49:00
Block: 1345061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76456 RingCT/type: yes/0
Extra: 01d514c9814611148d22baf56cf00e64693243e81081a3d7c765b2379ee26441f9021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9d62370e741c21a3fb93ff3f1f4ee6a3f9ef8648cf1f185b0193013d11bd14d4 0.600000000000 1832950 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1345071, "vin": [ { "gen": { "height": 1345061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9d62370e741c21a3fb93ff3f1f4ee6a3f9ef8648cf1f185b0193013d11bd14d4" } } ], "extra": [ 1, 213, 20, 201, 129, 70, 17, 20, 141, 34, 186, 245, 108, 240, 14, 100, 105, 50, 67, 232, 16, 129, 163, 215, 199, 101, 178, 55, 158, 226, 100, 65, 249, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8