Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d411e343285d83060fa337252f07929d08a29b50f708d1edce3dcfab4a876a12

Tx prefix hash: 6b5b84aa25d298694456c082dd943c2587f196fc3db8af443198373e6707ed69
Tx public key: d31a57882adae6b77d1e68b4ae5de5ebe19e1ed3c346ac86e3608d7ab037f43e
Timestamp: 1729122063 Timestamp [UCT]: 2024-10-16 23:41:03 Age [y:d:h:m:s]: 00:038:07:18:14
Block: 1133185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27333 RingCT/type: yes/0
Extra: 01d31a57882adae6b77d1e68b4ae5de5ebe19e1ed3c346ac86e3608d7ab037f43e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10eb08a3ce43eb03545b6fdec707d311c19a8bdd3c0aebc7c5ad5c120ac05dd3 0.600000000000 1616256 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": 1133195, "vin": [ { "gen": { "height": 1133185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10eb08a3ce43eb03545b6fdec707d311c19a8bdd3c0aebc7c5ad5c120ac05dd3" } } ], "extra": [ 1, 211, 26, 87, 136, 42, 218, 230, 183, 125, 30, 104, 180, 174, 93, 229, 235, 225, 158, 30, 211, 195, 70, 172, 134, 227, 96, 141, 122, 176, 55, 244, 62, 2, 17, 0, 0, 0, 3, 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