Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 423afb51c167585086ba8dcf0af62c041ea892d3eb6cf49f74afbd6fe7a70359

Tx prefix hash: c3d1b4648864569ac0c52a86280a1c5874f9c50d5a732b83525d1545434d140e
Tx public key: 0f8d43ba2e10be64742e3d4557c79ad8588c44a2ceedd8a7ee2ffee2d892d1f5
Timestamp: 1634244125 Timestamp [UCT]: 2021-10-14 20:42:05 Age [y:d:h:m:s]: 03:111:17:06:18
Block: 353101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 857434 RingCT/type: yes/0
Extra: 010f8d43ba2e10be64742e3d4557c79ad8588c44a2ceedd8a7ee2ffee2d892d1f50211000000035410958b000000000000000000

1 output(s) for total of 41.500382440000 dcy

stealth address amount amount idx
00: 50866b16e1338c96aac4029db2da5cc6bf50dededd003c6c75378e788dda11ab 41.500382440000 721595 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": 353111, "vin": [ { "gen": { "height": 353101 } } ], "vout": [ { "amount": 41500382440, "target": { "key": "50866b16e1338c96aac4029db2da5cc6bf50dededd003c6c75378e788dda11ab" } } ], "extra": [ 1, 15, 141, 67, 186, 46, 16, 190, 100, 116, 46, 61, 69, 87, 199, 154, 216, 88, 140, 68, 162, 206, 237, 216, 167, 238, 47, 254, 226, 216, 146, 209, 245, 2, 17, 0, 0, 0, 3, 84, 16, 149, 139, 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