Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ff1692b08498b15f88d7d6daf773bf20e5c6156ec3056009ac0e06d2138c8e0

Tx prefix hash: de9502fd0a33b6c803fa2aff805993b12d32f37fda868bf1d3d90adc61375292
Tx public key: f6a741fe1f474e570ecd1b1bc5238b5fb94d251ffee69da0132c690f81703747
Timestamp: 1709252947 Timestamp [UCT]: 2024-03-01 00:29:07 Age [y:d:h:m:s]: 01:021:08:58:39
Block: 968468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276276 RingCT/type: yes/0
Extra: 01f6a741fe1f474e570ecd1b1bc5238b5fb94d251ffee69da0132c690f8170374702110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1779f9c0d278527f136870e1daf53a0caeaab704cd2b9d434090059aff6c013 0.600000000000 1428283 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": 968478, "vin": [ { "gen": { "height": 968468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1779f9c0d278527f136870e1daf53a0caeaab704cd2b9d434090059aff6c013" } } ], "extra": [ 1, 246, 167, 65, 254, 31, 71, 78, 87, 14, 205, 27, 27, 197, 35, 139, 95, 185, 77, 37, 31, 254, 230, 157, 160, 19, 44, 105, 15, 129, 112, 55, 71, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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