Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae40f844540fb8028043e9d27fc57dad7c5612bbaf6ae9b3148ab30e3927ede

Tx prefix hash: 776145118b9f7f3034750a9cf4b7220d8c45cf3aca77f6d727e9ac3b39acf85b
Tx public key: ccc868adb1250a050c8bb1ae8ee91efa80c404b373419b1bbc2cf5101b0f0621
Timestamp: 1737464437 Timestamp [UCT]: 2025-01-21 13:00:37 Age [y:d:h:m:s]: 00:148:07:19:46
Block: 1202153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105726 RingCT/type: yes/0
Extra: 01ccc868adb1250a050c8bb1ae8ee91efa80c404b373419b1bbc2cf5101b0f06210211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ff6bdce16f7cc6ad2fb4976721f607a794f057d3059312c5a4d2e79859c14c1d 0.600000000000 1688814 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": 1202163, "vin": [ { "gen": { "height": 1202153 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ff6bdce16f7cc6ad2fb4976721f607a794f057d3059312c5a4d2e79859c14c1d" } } ], "extra": [ 1, 204, 200, 104, 173, 177, 37, 10, 5, 12, 139, 177, 174, 142, 233, 30, 250, 128, 196, 4, 179, 115, 65, 155, 27, 188, 44, 245, 16, 27, 15, 6, 33, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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