Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fb3514fb7bd1afd7a0cc4b242aa8cbfb3b46a03eb89a54bc1d0fa34ac76e02c

Tx prefix hash: 1445d5559b560ec4b9da4043e1a488ba9f8efc6ec274c4ae5513426c6fb86feb
Tx public key: 4b3a6d92863276853009a1e54eef8fe9160a1196023da42b8c6a649751bf7fec
Timestamp: 1765422800 Timestamp [UCT]: 2025-12-11 03:13:20 Age [y:d:h:m:s]: 00:021:16:56:46
Block: 1430999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 15546 RingCT/type: yes/0
Extra: 014b3a6d92863276853009a1e54eef8fe9160a1196023da42b8c6a649751bf7fec02110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6482942274beb486e7985e086a52dd7ae0717aa8c24f1d65f0fc752fecb5bc4f 0.600000000000 1919752 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": 1431009, "vin": [ { "gen": { "height": 1430999 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6482942274beb486e7985e086a52dd7ae0717aa8c24f1d65f0fc752fecb5bc4f" } } ], "extra": [ 1, 75, 58, 109, 146, 134, 50, 118, 133, 48, 9, 161, 229, 78, 239, 143, 233, 22, 10, 17, 150, 2, 61, 164, 43, 140, 106, 100, 151, 81, 191, 127, 236, 2, 17, 0, 0, 0, 2, 112, 96, 157, 3, 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