Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d38654daf13cd61778714b9603d6d159477a48e97d71dd060c363e60c1fe32

Tx prefix hash: 60f7a6de94aa43bfdf75f50d1248931187ad396e896341e9041c8c95f962f3f5
Tx public key: 5313e9e063f87acca1d6f4dc004610f0ef0c34dbfaa0788fdc1f9e1f0d6e5b7e
Timestamp: 1575977769 Timestamp [UCT]: 2019-12-10 11:36:09 Age [y:d:h:m:s]: 05:062:14:47:34
Block: 24847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1190363 RingCT/type: yes/0
Extra: 015313e9e063f87acca1d6f4dc004610f0ef0c34dbfaa0788fdc1f9e1f0d6e5b7e0211000000169159db1e000000000000000000

1 output(s) for total of 507.776320632000 dcy

stealth address amount amount idx
00: a28be32c83ff2effa52ae44e9d7bffb389dd663c973e408405112dee3a112e9f 507.776320632000 40806 of 0

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": 24857, "vin": [ { "gen": { "height": 24847 } } ], "vout": [ { "amount": 507776320632, "target": { "key": "a28be32c83ff2effa52ae44e9d7bffb389dd663c973e408405112dee3a112e9f" } } ], "extra": [ 1, 83, 19, 233, 224, 99, 248, 122, 204, 161, 214, 244, 220, 0, 70, 16, 240, 239, 12, 52, 219, 250, 160, 120, 143, 220, 31, 158, 31, 13, 110, 91, 126, 2, 17, 0, 0, 0, 22, 145, 89, 219, 30, 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