Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25b7d1cd7065c304cfd64ff9f62f62f0ee3ae8134dcec3be76ed4eba98d32568

Tx prefix hash: d7a625d63aa88635ea3620ff136a33dc6fb2f88b3cabd6c31a22d25ad285164e
Tx public key: 2a7bce65d4e22c9c00e2fed4d28289bf8282bcdb628c461f29400f627139ca4a
Timestamp: 1704392634 Timestamp [UCT]: 2024-01-04 18:23:54 Age [y:d:h:m:s]: 01:162:11:31:42
Block: 928163 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377171 RingCT/type: yes/0
Extra: 012a7bce65d4e22c9c00e2fed4d28289bf8282bcdb628c461f29400f627139ca4a02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 267c119709844b7bd27d500b44a8b5981eb5897d343524fdbdfc66f251e0aeeb 0.600000000000 1386021 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": 928173, "vin": [ { "gen": { "height": 928163 } } ], "vout": [ { "amount": 600000000, "target": { "key": "267c119709844b7bd27d500b44a8b5981eb5897d343524fdbdfc66f251e0aeeb" } } ], "extra": [ 1, 42, 123, 206, 101, 212, 226, 44, 156, 0, 226, 254, 212, 210, 130, 137, 191, 130, 130, 188, 219, 98, 140, 70, 31, 41, 64, 15, 98, 113, 57, 202, 74, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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