Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5be2e010b24518a92bdb5c23a4675c858bcb86f243330499275fd4e0408336a9

Tx prefix hash: 54d64baa5d5ee448cbb02a8dcd5660561e8a23649170f78e4bb6f25e5ff2b419
Tx public key: 7b2c0462e0c431b467c097d9b83a3b91f66a850e30638846fa2de6ff35afe9cc
Timestamp: 1732393068 Timestamp [UCT]: 2024-11-23 20:17:48 Age [y:d:h:m:s]: 00:129:12:45:41
Block: 1160198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92384 RingCT/type: yes/0
Extra: 017b2c0462e0c431b467c097d9b83a3b91f66a850e30638846fa2de6ff35afe9cc0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a292a64ca2753738182bb63c17343346c92e30797fd83e287c5dd2f8682d2178 0.600000000000 1645841 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": 1160208, "vin": [ { "gen": { "height": 1160198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a292a64ca2753738182bb63c17343346c92e30797fd83e287c5dd2f8682d2178" } } ], "extra": [ 1, 123, 44, 4, 98, 224, 196, 49, 180, 103, 192, 151, 217, 184, 58, 59, 145, 246, 106, 133, 14, 48, 99, 136, 70, 250, 45, 230, 255, 53, 175, 233, 204, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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