Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a7ad6f9127af82c28f9849cd3d2f5ac4ec65f747349c493fb1e3ddd71dd88a3

Tx prefix hash: b6fb29f379dc22ed6a1a61c79c7ea9aec159d7e7d2822583014ec58af88b39a2
Tx public key: d285346d4fd8be8dc856828b989e2f9d1354ddd6809cb5dc06ecf1a322b04e14
Timestamp: 1725614462 Timestamp [UCT]: 2024-09-06 09:21:02 Age [y:d:h:m:s]: 00:169:19:24:56
Block: 1104111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121150 RingCT/type: yes/0
Extra: 01d285346d4fd8be8dc856828b989e2f9d1354ddd6809cb5dc06ecf1a322b04e14021100000014e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b87fa392840f70deceba082ab2f7428167fc804ab9896ba9c217e71fcb53ee8 0.600000000000 1581178 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": 1104121, "vin": [ { "gen": { "height": 1104111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b87fa392840f70deceba082ab2f7428167fc804ab9896ba9c217e71fcb53ee8" } } ], "extra": [ 1, 210, 133, 52, 109, 79, 216, 190, 141, 200, 86, 130, 139, 152, 158, 47, 157, 19, 84, 221, 214, 128, 156, 181, 220, 6, 236, 241, 163, 34, 176, 78, 20, 2, 17, 0, 0, 0, 20, 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