Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1607b61907a23fd595eff35db3ca712556d9e4a7f401b1f1152b0b4cb7a7955f

Tx prefix hash: 8c869cfd9d792820b1c9500624af2b7abaf304adc485dbdbbea03882eb8a1a41
Tx public key: 2a5b78f6dba0e06285313b6c2fc7d5753ac8219da7f645325391c15387d0de29
Timestamp: 1728042406 Timestamp [UCT]: 2024-10-04 11:46:46 Age [y:d:h:m:s]: 00:110:07:38:11
Block: 1124236 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78818 RingCT/type: yes/0
Extra: 012a5b78f6dba0e06285313b6c2fc7d5753ac8219da7f645325391c15387d0de2902110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed065ae6cd3b40e063efd952f24170377c20bfed23284aaadcffdfea212c8841 0.600000000000 1606835 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": 1124246, "vin": [ { "gen": { "height": 1124236 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed065ae6cd3b40e063efd952f24170377c20bfed23284aaadcffdfea212c8841" } } ], "extra": [ 1, 42, 91, 120, 246, 219, 160, 224, 98, 133, 49, 59, 108, 47, 199, 213, 117, 58, 200, 33, 157, 167, 246, 69, 50, 83, 145, 193, 83, 135, 208, 222, 41, 2, 17, 0, 0, 0, 2, 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