Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2af3f4a0c295a9c39614973b601d62893b4406cec2d855497b4342b90d2ff4b

Tx prefix hash: bed7f7959b27fa8b05aadf198b66021e8f5a3a1f0a4d14909a2f9dd9c3e39488
Tx public key: 5a0fe852b80cd1b26d8bc95cf0df0c0426ec59c2f7cd3df03faa5e210907aaf3
Timestamp: 1578181916 Timestamp [UCT]: 2020-01-04 23:51:56 Age [y:d:h:m:s]: 05:106:03:45:35
Block: 38859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1225724 RingCT/type: yes/0
Extra: 015a0fe852b80cd1b26d8bc95cf0df0c0426ec59c2f7cd3df03faa5e210907aaf302110000000dd81c26c0000000000000000000

1 output(s) for total of 456.346347791000 dcy

stealth address amount amount idx
00: f10fa36d2491343707b0ee1110ec7a6eaccf36f24edb79eefdb3b57e7e3cf92b 456.346347791000 66558 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": 38869, "vin": [ { "gen": { "height": 38859 } } ], "vout": [ { "amount": 456346347791, "target": { "key": "f10fa36d2491343707b0ee1110ec7a6eaccf36f24edb79eefdb3b57e7e3cf92b" } } ], "extra": [ 1, 90, 15, 232, 82, 184, 12, 209, 178, 109, 139, 201, 92, 240, 223, 12, 4, 38, 236, 89, 194, 247, 205, 61, 240, 63, 170, 94, 33, 9, 7, 170, 243, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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