Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ff21481321f8212371dbaec103c9a717d578f0fe3feaa7b7b0d2d9bd59d079

Tx prefix hash: 02aa2fe9e7a0921a54928e6f31f8d0f3516fbfad3f762cd326bbc338e4c361b1
Tx public key: 780e019e7756da33835f73a2774a85b5efab83a3757279c7150d9370b7ffbf3e
Timestamp: 1741275345 Timestamp [UCT]: 2025-03-06 15:35:45 Age [y:d:h:m:s]: 00:006:02:03:37
Block: 1233486 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4356 RingCT/type: yes/0
Extra: 01780e019e7756da33835f73a2774a85b5efab83a3757279c7150d9370b7ffbf3e021100000015007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb5e6dbbcf1961953bf62a2d0d59eb4f0312ecfb084c44c26242c7abdb46e8a3 0.600000000000 1720407 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": 1233496, "vin": [ { "gen": { "height": 1233486 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb5e6dbbcf1961953bf62a2d0d59eb4f0312ecfb084c44c26242c7abdb46e8a3" } } ], "extra": [ 1, 120, 14, 1, 158, 119, 86, 218, 51, 131, 95, 115, 162, 119, 74, 133, 181, 239, 171, 131, 163, 117, 114, 121, 199, 21, 13, 147, 112, 183, 255, 191, 62, 2, 17, 0, 0, 0, 21, 0, 127, 151, 138, 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