Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41735e7e659fabaf39aa5543313831789c93de719b20307f4adab71f63cd4c7c

Tx prefix hash: 0a4cb9153f1fa993a66b977026767591e3e54f01a6f5c18e75b70a7cd5b718a6
Tx public key: 9e536cb8643c0ec528092dcaf72ee3a7f04c0f8cfbc64863f1429f595161f902
Timestamp: 1703228951 Timestamp [UCT]: 2023-12-22 07:09:11 Age [y:d:h:m:s]: 01:334:20:04:43
Block: 918513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498149 RingCT/type: yes/0
Extra: 019e536cb8643c0ec528092dcaf72ee3a7f04c0f8cfbc64863f1429f595161f90202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d67126d98777b9106bf5f21c3a369fa407c35fc8ab700e43ecac35cb9b6f8e6d 0.600000000000 1376157 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": 918523, "vin": [ { "gen": { "height": 918513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d67126d98777b9106bf5f21c3a369fa407c35fc8ab700e43ecac35cb9b6f8e6d" } } ], "extra": [ 1, 158, 83, 108, 184, 100, 60, 14, 197, 40, 9, 45, 202, 247, 46, 227, 167, 240, 76, 15, 140, 251, 198, 72, 99, 241, 66, 159, 89, 81, 97, 249, 2, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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