Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 719055264e74b0b307c48c2291b43ed26abc45e55df78b6d7608fb8a03ff7281

Tx prefix hash: 27a6d6edf58301001f623d3ced960eea23ea396880fe6a12c0906e8c835e65e8
Tx public key: a00fb77ef1a0f6f2acda14451c539d74186c2763d671125d9d065e833887d20e
Timestamp: 1712911428 Timestamp [UCT]: 2024-04-12 08:43:48 Age [y:d:h:m:s]: 00:350:15:27:19
Block: 998770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250701 RingCT/type: yes/0
Extra: 01a00fb77ef1a0f6f2acda14451c539d74186c2763d671125d9d065e833887d20e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 659c40a6c9ad5c142eccbd63f20ebf8722029da2a5e17f88c86b664b39373f43 0.600000000000 1459224 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": 998780, "vin": [ { "gen": { "height": 998770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "659c40a6c9ad5c142eccbd63f20ebf8722029da2a5e17f88c86b664b39373f43" } } ], "extra": [ 1, 160, 15, 183, 126, 241, 160, 246, 242, 172, 218, 20, 69, 28, 83, 157, 116, 24, 108, 39, 99, 214, 113, 18, 93, 157, 6, 94, 131, 56, 135, 210, 14, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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