Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58a3698c1a4371b72c7f630af117023e3697781a003c16ce56d3fa07fd27d836

Tx prefix hash: bb0e44ba861fa90bb2f67365ae2eba1ca6933b2722b99b514f41a3812b83ae63
Tx public key: 6df8773fdd0915ad8ffa66b116f401a812e9c669ae7a9f60165ef73d986ba6b7
Timestamp: 1762031310 Timestamp [UCT]: 2025-11-01 21:08:30 Age [y:d:h:m:s]: 00:003:18:33:48
Block: 1402899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2691 RingCT/type: yes/0
Extra: 016df8773fdd0915ad8ffa66b116f401a812e9c669ae7a9f60165ef73d986ba6b702110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af8df4cca6a8b1a920dcaf7c10202ebc22fadafa55c81c1f427b8e2406fe1af4 0.600000000000 1891224 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": 1402909, "vin": [ { "gen": { "height": 1402899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af8df4cca6a8b1a920dcaf7c10202ebc22fadafa55c81c1f427b8e2406fe1af4" } } ], "extra": [ 1, 109, 248, 119, 63, 221, 9, 21, 173, 143, 250, 102, 177, 22, 244, 1, 168, 18, 233, 198, 105, 174, 122, 159, 96, 22, 94, 247, 61, 152, 107, 166, 183, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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