Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 916e65aeddcf3dd547e3205cb8c4ba7929587284cfc02f3a8ba63e73bd8b0046

Tx prefix hash: a7592caada7abed093ce20723337f6d53a7762f2bebb5b799cc4bb994d9c7375
Tx public key: c5454cd770ff8b8770c8caf38c3f39c1520723c79ad6a223195728a3d8182fc4
Timestamp: 1711848858 Timestamp [UCT]: 2024-03-31 01:34:18 Age [y:d:h:m:s]: 01:036:18:07:03
Block: 989994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287241 RingCT/type: yes/0
Extra: 01c5454cd770ff8b8770c8caf38c3f39c1520723c79ad6a223195728a3d8182fc40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 103d6f7a5962588e6b7e991aaf3635a87e4a5b8fb1f73e4d291fc03e08f171f9 0.600000000000 1450312 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": 990004, "vin": [ { "gen": { "height": 989994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "103d6f7a5962588e6b7e991aaf3635a87e4a5b8fb1f73e4d291fc03e08f171f9" } } ], "extra": [ 1, 197, 69, 76, 215, 112, 255, 139, 135, 112, 200, 202, 243, 140, 63, 57, 193, 82, 7, 35, 199, 154, 214, 162, 35, 25, 87, 40, 163, 216, 24, 47, 196, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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