Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a04bfd8c9c22e922a1a2415dde80c8ab95826c18dafd322ca45d6cbde8107333

Tx prefix hash: 8e6439fbbd7414386505a567e1ffb6a11bcd707df0b37b1725e1d0fe8b3a8822
Tx public key: 53934ffedb4e88c73e2e6af3f3de12a74df98376468791f67b8d70934fb38c04
Timestamp: 1762066604 Timestamp [UCT]: 2025-11-02 06:56:44 Age [y:d:h:m:s]: 00:006:18:00:12
Block: 1403194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4822 RingCT/type: yes/0
Extra: 0153934ffedb4e88c73e2e6af3f3de12a74df98376468791f67b8d70934fb38c040211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c50e4ff3bf20585f4bc814a40e521e71aa4f95453aeb32ad1a14734c9b74b362 0.600000000000 1891521 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": 1403204, "vin": [ { "gen": { "height": 1403194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c50e4ff3bf20585f4bc814a40e521e71aa4f95453aeb32ad1a14734c9b74b362" } } ], "extra": [ 1, 83, 147, 79, 254, 219, 78, 136, 199, 62, 46, 106, 243, 243, 222, 18, 167, 77, 249, 131, 118, 70, 135, 145, 246, 123, 141, 112, 147, 79, 179, 140, 4, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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