Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e82962bb52948c2c873e56ad0c65e1ae4d5cbe71c298caa2496bfe9006c107c

Tx prefix hash: 5358ec5ebcec62b7e9b688b34070d60ef94676aae66e2aacbc3e3c0402a4d9b1
Tx public key: c1906394df9dce9a0935889b7237f6a6323556c3d269e7e88919e1708c22b2da
Timestamp: 1760257405 Timestamp [UCT]: 2025-10-12 08:23:25 Age [y:d:h:m:s]: 00:039:13:59:55
Block: 1388186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28343 RingCT/type: yes/0
Extra: 01c1906394df9dce9a0935889b7237f6a6323556c3d269e7e88919e1708c22b2da021100000009163191ee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5594234cef98c1d6781a4d07b98b441779ee3607140db94e381a82bae4043d2e 0.600000000000 1876385 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": 1388196, "vin": [ { "gen": { "height": 1388186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5594234cef98c1d6781a4d07b98b441779ee3607140db94e381a82bae4043d2e" } } ], "extra": [ 1, 193, 144, 99, 148, 223, 157, 206, 154, 9, 53, 136, 155, 114, 55, 246, 166, 50, 53, 86, 195, 210, 105, 231, 232, 137, 25, 225, 112, 140, 34, 178, 218, 2, 17, 0, 0, 0, 9, 22, 49, 145, 238, 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