Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6322ac5a9f0b9f71d702f32db03c19065896cd57f1da88f7e090f84d3236214e

Tx prefix hash: 6034b970e5bbed3bdfcc5164290e2045c46422d6e1ac2e15a7ebdfdda5ea339e
Tx public key: ab0d3d2dca5006e891d478f7c33603cb9efd7855b5730054821fdb52a8bc5f92
Timestamp: 1705533591 Timestamp [UCT]: 2024-01-17 23:19:51 Age [y:d:h:m:s]: 01:307:08:41:38
Block: 937599 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478506 RingCT/type: yes/0
Extra: 01ab0d3d2dca5006e891d478f7c33603cb9efd7855b5730054821fdb52a8bc5f920211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 963a9ae7ac60418e2716394d41edb4fd44757d81138fa81cbfba367a78be2f08 0.600000000000 1395659 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": 937609, "vin": [ { "gen": { "height": 937599 } } ], "vout": [ { "amount": 600000000, "target": { "key": "963a9ae7ac60418e2716394d41edb4fd44757d81138fa81cbfba367a78be2f08" } } ], "extra": [ 1, 171, 13, 61, 45, 202, 80, 6, 232, 145, 212, 120, 247, 195, 54, 3, 203, 158, 253, 120, 85, 181, 115, 0, 84, 130, 31, 219, 82, 168, 188, 95, 146, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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