Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d294c29d986f8a749091b3f93de4c46dc2c9e54f88ad1d33ada521ef937c36a4

Tx prefix hash: 94e118d72fbac3ed3e3dcfad09705345a811e3c7acf3e55e9726c49ccc2d6269
Tx public key: 860114b8eadb0c63ce5fc87f3e58bff0cf28b9385c7abad83a940019bfcd22af
Timestamp: 1694841732 Timestamp [UCT]: 2023-09-16 05:22:12 Age [y:d:h:m:s]: 01:206:00:12:19
Block: 849165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408321 RingCT/type: yes/0
Extra: 01860114b8eadb0c63ce5fc87f3e58bff0cf28b9385c7abad83a940019bfcd22af0211000000084b8f5122000000000000000000

1 output(s) for total of 0.942679163000 dcy

stealth address amount amount idx
00: 4a4c4f5addfa4d1d3d62f0a129328b053d1d3293b14f83f362e947beaa1f96b3 0.942679163000 1302811 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": 849175, "vin": [ { "gen": { "height": 849165 } } ], "vout": [ { "amount": 942679163, "target": { "key": "4a4c4f5addfa4d1d3d62f0a129328b053d1d3293b14f83f362e947beaa1f96b3" } } ], "extra": [ 1, 134, 1, 20, 184, 234, 219, 12, 99, 206, 95, 200, 127, 62, 88, 191, 240, 207, 40, 185, 56, 92, 122, 186, 216, 58, 148, 0, 25, 191, 205, 34, 175, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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