Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7d811a10fb0e7d8808c033318361d62209b5331417d8a04b660efcfb53f406e

Tx prefix hash: bb922fafe3658f05fec3476863c1068b2009fde7ac65c15bdc69ad9dc57ad2a6
Tx public key: 933e82615527cd1bcf1fe9d6aac876f9e8975da08f4d4df2b3fb2ea82e8e08ce
Timestamp: 1725021287 Timestamp [UCT]: 2024-08-30 12:34:47 Age [y:d:h:m:s]: 00:291:05:56:34
Block: 1099181 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207936 RingCT/type: yes/0
Extra: 01933e82615527cd1bcf1fe9d6aac876f9e8975da08f4d4df2b3fb2ea82e8e08ce02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7160ee4ace078d19f9be1d96cb51d85fcb7d0ce309e211c8419f1c59413da87 0.600000000000 1575112 of 15

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": 1099191, "vin": [ { "gen": { "height": 1099181 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7160ee4ace078d19f9be1d96cb51d85fcb7d0ce309e211c8419f1c59413da87" } } ], "extra": [ 1, 147, 62, 130, 97, 85, 39, 205, 27, 207, 31, 233, 214, 170, 200, 118, 249, 232, 151, 93, 160, 143, 77, 77, 242, 179, 251, 46, 168, 46, 142, 8, 206, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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