Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7be99e60ed0572f53ab9cde276127df5dd4517922a7f67361c49c95e5af1e6dc

Tx prefix hash: 6eef37ebb37ca28ef408f191d81de7fffdbb3f7ec3286ac92d6f2e00bbef1a50
Tx public key: 05978732b8feeeaa5e5c848be99a39518ece5cee2bf0abbd84a9a56eee4d603d
Timestamp: 1766270874 Timestamp [UCT]: 2025-12-20 22:47:54 Age [y:d:h:m:s]: 00:000:11:23:04
Block: 1438031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330 RingCT/type: yes/0
Extra: 0105978732b8feeeaa5e5c848be99a39518ece5cee2bf0abbd84a9a56eee4d603d0211000000027b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f8cb63d19caee9e693afc216bd3e0c5f4fe2d0d4cc01bb6dddb315521819d1c 0.600000000000 1926846 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": 1438041, "vin": [ { "gen": { "height": 1438031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f8cb63d19caee9e693afc216bd3e0c5f4fe2d0d4cc01bb6dddb315521819d1c" } } ], "extra": [ 1, 5, 151, 135, 50, 184, 254, 238, 170, 94, 92, 132, 139, 233, 154, 57, 81, 142, 206, 92, 238, 43, 240, 171, 189, 132, 169, 165, 110, 238, 77, 96, 61, 2, 17, 0, 0, 0, 2, 123, 30, 81, 172, 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