Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34d344474f44ee74355bdb647746998e30e73df0d39407e5450c631ca7d5c262

Tx prefix hash: 8a2617c6ca63584cdb1798827a47e140149a4b3a8eb4299461c48f96a9148fff
Tx public key: 569771e455beb71ad6c46d5e4727d3b411fe29b284cb1f7df133510246894f2f
Timestamp: 1729344384 Timestamp [UCT]: 2024-10-19 13:26:24 Age [y:d:h:m:s]: 00:166:09:58:59
Block: 1135026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118707 RingCT/type: yes/0
Extra: 01569771e455beb71ad6c46d5e4727d3b411fe29b284cb1f7df133510246894f2f021100000011007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4570b9637ad4e763f80b8f2c297fd2a7af75b0d1ab93b249101a0c160ae71555 0.600000000000 1618355 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": 1135036, "vin": [ { "gen": { "height": 1135026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4570b9637ad4e763f80b8f2c297fd2a7af75b0d1ab93b249101a0c160ae71555" } } ], "extra": [ 1, 86, 151, 113, 228, 85, 190, 183, 26, 214, 196, 109, 94, 71, 39, 211, 180, 17, 254, 41, 178, 132, 203, 31, 125, 241, 51, 81, 2, 70, 137, 79, 47, 2, 17, 0, 0, 0, 17, 0, 127, 151, 138, 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