Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 159d0b93d26dd428d8fc3b71ecf98670244127123200c4eacdadecbe9ea1ca6e

Tx prefix hash: 04b32867ed3fec8430ac71fcd8ab08ce44aef23172626997c9c2543a91b075d3
Tx public key: 18fe7ba47a1901ff66c1271aa6252fbe283b661f4dbeb6025fb17afed062e6c2
Timestamp: 1700424436 Timestamp [UCT]: 2023-11-19 20:07:16 Age [y:d:h:m:s]: 01:069:08:22:51
Block: 895264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310733 RingCT/type: yes/0
Extra: 0118fe7ba47a1901ff66c1271aa6252fbe283b661f4dbeb6025fb17afed062e6c2021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.663160601000 dcy

stealth address amount amount idx
00: f7c363931fb522f0ed364d60c934f588651b25690b0bbb221d4c0dd8a505f217 0.663160601000 1351493 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": 895274, "vin": [ { "gen": { "height": 895264 } } ], "vout": [ { "amount": 663160601, "target": { "key": "f7c363931fb522f0ed364d60c934f588651b25690b0bbb221d4c0dd8a505f217" } } ], "extra": [ 1, 24, 254, 123, 164, 122, 25, 1, 255, 102, 193, 39, 26, 166, 37, 47, 190, 40, 59, 102, 31, 77, 190, 182, 2, 95, 177, 122, 254, 208, 98, 230, 194, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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