Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f5cf0bc55ea71a6b805f7b3f9c010b8bfc45ac90a7defafc9881b4d2065a85a

Tx prefix hash: 513f92958316d9b57abedf1ae740ce9585980e94c321e3c20dd9b636c45cf7b7
Tx public key: c25fa5500aee9c142552d6148f7ef8b7049cec93015eb297c7bf6527bf01026d
Timestamp: 1671137715 Timestamp [UCT]: 2022-12-15 20:55:15 Age [y:d:h:m:s]: 01:253:20:40:16
Block: 653357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442394 RingCT/type: yes/0
Extra: 01c25fa5500aee9c142552d6148f7ef8b7049cec93015eb297c7bf6527bf01026d02110000000175e3f0e9000000000000000000

1 output(s) for total of 4.199107753000 dcy

stealth address amount amount idx
00: fa0491c53df5335abcc1c0c40a033f0664f5b0e80200e81b7acaa71ed0a8f7ce 4.199107753000 1093820 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": 653367, "vin": [ { "gen": { "height": 653357 } } ], "vout": [ { "amount": 4199107753, "target": { "key": "fa0491c53df5335abcc1c0c40a033f0664f5b0e80200e81b7acaa71ed0a8f7ce" } } ], "extra": [ 1, 194, 95, 165, 80, 10, 238, 156, 20, 37, 82, 214, 20, 143, 126, 248, 183, 4, 156, 236, 147, 1, 94, 178, 151, 199, 191, 101, 39, 191, 1, 2, 109, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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