Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 734be854f9c149a89bbed7ada4cd0f81b94db80cfcebc87fa5baacd214ddf7e8

Tx prefix hash: 019816ab55229c13388245b6d04a7b888a067d3d0a6258e158313dfff14d7ef0
Tx public key: 51f4e0f714512876c217373104d8c45be4d7a583190950069a1be4d4b398c023
Timestamp: 1736096998 Timestamp [UCT]: 2025-01-05 17:09:58 Age [y:d:h:m:s]: 00:162:11:27:29
Block: 1190881 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115827 RingCT/type: yes/0
Extra: 0151f4e0f714512876c217373104d8c45be4d7a583190950069a1be4d4b398c02302110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 276001b9e934f04f19ddc28a76ab5e3c8a8c5cca0fb95857ab16203c31fd2ee7 0.600000000000 1677404 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": 1190891, "vin": [ { "gen": { "height": 1190881 } } ], "vout": [ { "amount": 600000000, "target": { "key": "276001b9e934f04f19ddc28a76ab5e3c8a8c5cca0fb95857ab16203c31fd2ee7" } } ], "extra": [ 1, 81, 244, 224, 247, 20, 81, 40, 118, 194, 23, 55, 49, 4, 216, 196, 91, 228, 215, 165, 131, 25, 9, 80, 6, 154, 27, 228, 212, 179, 152, 192, 35, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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