Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c45f0c30f7e87f0207cc0dfea949c7addad31148afb249d502c29d756b364298

Tx prefix hash: fc4ecd7be5da3f0027753ec26f17e0ce5bf9dc20b332c43716e7860c4d573cd6
Tx public key: 6b3cc1a2510316e6e98b084440291e361ea8cd3e60e133ca30af6c5bb48bf4c3
Timestamp: 1720620120 Timestamp [UCT]: 2024-07-10 14:02:00 Age [y:d:h:m:s]: 00:258:08:36:47
Block: 1062700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184572 RingCT/type: yes/0
Extra: 016b3cc1a2510316e6e98b084440291e361ea8cd3e60e133ca30af6c5bb48bf4c302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca60a31d7e92cf0966b18332fc7db849423d0e3f8d829e5a33f4e22f8eb6540d 0.600000000000 1533207 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": 1062710, "vin": [ { "gen": { "height": 1062700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca60a31d7e92cf0966b18332fc7db849423d0e3f8d829e5a33f4e22f8eb6540d" } } ], "extra": [ 1, 107, 60, 193, 162, 81, 3, 22, 230, 233, 139, 8, 68, 64, 41, 30, 54, 30, 168, 205, 62, 96, 225, 51, 202, 48, 175, 108, 91, 180, 139, 244, 195, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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