Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 180bd56cd3c35db5f498be66d4a605fc343c718be70e812c213f5d1c5d3d666c

Tx prefix hash: b307511d3fa56acc9fb6eb059d9fc68d2da82eea1232537d777150e02821c6d9
Tx public key: 96cc12fb6357f8f915324a2ab63757eec74b8dd250281c4f7f6a7bb6a8ceb9e8
Timestamp: 1715089394 Timestamp [UCT]: 2024-05-07 13:43:14 Age [y:d:h:m:s]: 00:191:20:36:23
Block: 1016853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 137328 RingCT/type: yes/0
Extra: 0196cc12fb6357f8f915324a2ab63757eec74b8dd250281c4f7f6a7bb6a8ceb9e80211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 48fd5526ee14689ec57ea4cfd7d72328ec5ee8073c2e5a7b9ece603f6e257588 0.600000000000 1480558 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": 1016863, "vin": [ { "gen": { "height": 1016853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "48fd5526ee14689ec57ea4cfd7d72328ec5ee8073c2e5a7b9ece603f6e257588" } } ], "extra": [ 1, 150, 204, 18, 251, 99, 87, 248, 249, 21, 50, 74, 42, 182, 55, 87, 238, 199, 75, 141, 210, 80, 40, 28, 79, 127, 106, 123, 182, 168, 206, 185, 232, 2, 17, 0, 0, 0, 7, 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