Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7fd7ffd58497c5666d8d60effc5abef4d636e51d36457d47bed3a532c42d25

Tx prefix hash: d3979c5c4a44cdc6610c4baa8f176dc477c3d2e453e60eefd9c3e389a9301e8b
Tx public key: 60b49c9ecb1578114e77125f344a1e634e978dd0d1bf82459b2e28e9fa7c6ac4
Timestamp: 1576927505 Timestamp [UCT]: 2019-12-21 11:25:05 Age [y:d:h:m:s]: 05:144:18:45:17
Block: 29012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1252821 RingCT/type: yes/0
Extra: 0160b49c9ecb1578114e77125f344a1e634e978dd0d1bf82459b2e28e9fa7c6ac402110000001a9159db1e000000000000000000

1 output(s) for total of 491.894610603000 dcy

stealth address amount amount idx
00: 38aae486516e9af4c77cf1e1acdd10a420350d9834ce4485c637e5c6a89b49dc 491.894610603000 47832 of 0

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": 29022, "vin": [ { "gen": { "height": 29012 } } ], "vout": [ { "amount": 491894610603, "target": { "key": "38aae486516e9af4c77cf1e1acdd10a420350d9834ce4485c637e5c6a89b49dc" } } ], "extra": [ 1, 96, 180, 156, 158, 203, 21, 120, 17, 78, 119, 18, 95, 52, 74, 30, 99, 78, 151, 141, 208, 209, 191, 130, 69, 155, 46, 40, 233, 250, 124, 106, 196, 2, 17, 0, 0, 0, 26, 145, 89, 219, 30, 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