Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5763363a0426caa11d2b0ad720003aec871bda7418f4618ebd510f841989f152

Tx prefix hash: f1cae0b5f7b6e8418d0935f2e4e2c6bc2580f6941a68a2d20a924a2646710982
Tx public key: 96b2f2a6804800745dcca5f9e9d2aea2ddef118518de1d844124b69f8597f0c1
Timestamp: 1726509980 Timestamp [UCT]: 2024-09-16 18:06:20 Age [y:d:h:m:s]: 00:206:15:37:58
Block: 1111522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147527 RingCT/type: yes/0
Extra: 0196b2f2a6804800745dcca5f9e9d2aea2ddef118518de1d844124b69f8597f0c1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16047e3c4e3bb63a27c039076429b6eb763288f537fce00f33a2e76aeeada866 0.600000000000 1590513 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": 1111532, "vin": [ { "gen": { "height": 1111522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16047e3c4e3bb63a27c039076429b6eb763288f537fce00f33a2e76aeeada866" } } ], "extra": [ 1, 150, 178, 242, 166, 128, 72, 0, 116, 93, 204, 165, 249, 233, 210, 174, 162, 221, 239, 17, 133, 24, 222, 29, 132, 65, 36, 182, 159, 133, 151, 240, 193, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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