Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75b9775b3d4e02c465f5a7cdfc85b71fa055e21cf1789ae7064a505c5be257a1

Tx prefix hash: fa6b9ba6751098f4aedec2c813b2fadc0a4487970b6eb4ccf5cd8cd6594072bd
Tx public key: 76e2902ee539fa0c486fcc3c3a60acdbb9e60b573d4791083af3c852705ba8b3
Timestamp: 1731738733 Timestamp [UCT]: 2024-11-16 06:32:13 Age [y:d:h:m:s]: 00:186:10:28:45
Block: 1154793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133101 RingCT/type: yes/0
Extra: 0176e2902ee539fa0c486fcc3c3a60acdbb9e60b573d4791083af3c852705ba8b3021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5a8f5e4fa472f216daae80ae0c4f008127c50aed7b318e6f80dbae4262cea8e 0.600000000000 1640406 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": 1154803, "vin": [ { "gen": { "height": 1154793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5a8f5e4fa472f216daae80ae0c4f008127c50aed7b318e6f80dbae4262cea8e" } } ], "extra": [ 1, 118, 226, 144, 46, 229, 57, 250, 12, 72, 111, 204, 60, 58, 96, 172, 219, 185, 230, 11, 87, 61, 71, 145, 8, 58, 243, 200, 82, 112, 91, 168, 179, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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