Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 263d4c3dd16bd3e353a671867201c0e7328a5e80232f154b72ba9751f7929b17

Tx prefix hash: 39b652dca09f79a08d6e540543999dcbcc8cef026e26eba11c18bc4c4d653901
Tx public key: 1fb39f122eaac0c6836c3c08b52052a3dffc60fa2f15562d77151adccd37a10a
Timestamp: 1727335126 Timestamp [UCT]: 2024-09-26 07:18:46 Age [y:d:h:m:s]: 00:237:18:51:08
Block: 1118367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169803 RingCT/type: yes/0
Extra: 011fb39f122eaac0c6836c3c08b52052a3dffc60fa2f15562d77151adccd37a10a021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c4f5676bb0be8f9deb01853e96aed1b4789c37c84b0e1f5a95a9ba55858aeb 0.600000000000 1599534 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": 1118377, "vin": [ { "gen": { "height": 1118367 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c4f5676bb0be8f9deb01853e96aed1b4789c37c84b0e1f5a95a9ba55858aeb" } } ], "extra": [ 1, 31, 179, 159, 18, 46, 170, 192, 198, 131, 108, 60, 8, 181, 32, 82, 163, 223, 252, 96, 250, 47, 21, 86, 45, 119, 21, 26, 220, 205, 55, 161, 10, 2, 17, 0, 0, 0, 6, 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