Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d36ad78781c7292a6b6d48d2347bac7b2721c939d28b018bb9a852c59c3e4319

Tx prefix hash: 3a2907f4b1cf8115f66b83261e27f2a53e2b38259f4559172a47ae9bd9031217
Tx public key: 66eb4632b1f84d7710e1e72d1fc3ced727b0b2038608f272a72277ae42ba85f2
Timestamp: 1725630532 Timestamp [UCT]: 2024-09-06 13:48:52 Age [y:d:h:m:s]: 00:209:20:36:58
Block: 1104238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149828 RingCT/type: yes/0
Extra: 0166eb4632b1f84d7710e1e72d1fc3ced727b0b2038608f272a72277ae42ba85f2021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5775515b8c15de75a523af3002044615f63aef973840f6ba5d0e1a45ad578ed 0.600000000000 1581317 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": 1104248, "vin": [ { "gen": { "height": 1104238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5775515b8c15de75a523af3002044615f63aef973840f6ba5d0e1a45ad578ed" } } ], "extra": [ 1, 102, 235, 70, 50, 177, 248, 77, 119, 16, 225, 231, 45, 31, 195, 206, 215, 39, 176, 178, 3, 134, 8, 242, 114, 167, 34, 119, 174, 66, 186, 133, 242, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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