Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bafe20c2f798b216b762cfbfa65591ce07026914fbc77d4e97cea579997143b8

Tx prefix hash: 4c236225c1d0c420e658e0b8a184389ef071c823a765c75ef95e21002d66b6ad
Tx public key: 6d34222b0b3ac5d2f660f1ea3a66379e53bb25b85690aecf770a7c9d7aa3b33d
Timestamp: 1735044392 Timestamp [UCT]: 2024-12-24 12:46:32 Age [y:d:h:m:s]: 00:133:12:13:37
Block: 1182168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95221 RingCT/type: yes/0
Extra: 016d34222b0b3ac5d2f660f1ea3a66379e53bb25b85690aecf770a7c9d7aa3b33d0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e60db29667cb60f0423e226fd42ca742b79214f6a02be900ed4298392694735 0.600000000000 1668601 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": 1182178, "vin": [ { "gen": { "height": 1182168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e60db29667cb60f0423e226fd42ca742b79214f6a02be900ed4298392694735" } } ], "extra": [ 1, 109, 52, 34, 43, 11, 58, 197, 210, 246, 96, 241, 234, 58, 102, 55, 158, 83, 187, 37, 184, 86, 144, 174, 207, 119, 10, 124, 157, 122, 163, 179, 61, 2, 17, 0, 0, 0, 2, 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