Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 171d74cc940274e5ef1b9a5a871f8255190a9d2eed84f173026fc1c3fc0f2499

Tx prefix hash: d40716a9306228e5c425aed322201930813006df10a4a15e8b0726203d1e4090
Tx public key: 39932f9236372b400369602bf6c69410a9ac2d2c02dff8fb6da0b2093b9b6eb4
Timestamp: 1729964369 Timestamp [UCT]: 2024-10-26 17:39:29 Age [y:d:h:m:s]: 00:028:16:47:04
Block: 1140139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20481 RingCT/type: yes/0
Extra: 0139932f9236372b400369602bf6c69410a9ac2d2c02dff8fb6da0b2093b9b6eb40211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6467340d7f82f9ac338e4100fbe6665be24535d4e10da195e980305858a1a1e3 0.600000000000 1623934 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": 1140149, "vin": [ { "gen": { "height": 1140139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6467340d7f82f9ac338e4100fbe6665be24535d4e10da195e980305858a1a1e3" } } ], "extra": [ 1, 57, 147, 47, 146, 54, 55, 43, 64, 3, 105, 96, 43, 246, 198, 148, 16, 169, 172, 45, 44, 2, 223, 248, 251, 109, 160, 178, 9, 59, 155, 110, 180, 2, 17, 0, 0, 0, 9, 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