Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d761445a4ee81c91a55223aafee8fd79099e036de6c4f16241667740c4e513f

Tx prefix hash: 8c12abff8debfaeba694ceb35784d0bb8e0c609e25ec3192d38d8fd6a5d1600e
Tx public key: 021f9e4d06a7b57252706012d4d98af736fd2a39ca45fae22e000ca9969f8274
Timestamp: 1709307128 Timestamp [UCT]: 2024-03-01 15:32:08 Age [y:d:h:m:s]: 01:047:09:20:20
Block: 968913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294866 RingCT/type: yes/0
Extra: 01021f9e4d06a7b57252706012d4d98af736fd2a39ca45fae22e000ca9969f827402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c1fa09b56842a6e4548f55a55a10a83881065a16dc7ca49cd92d5e7916cf30b 0.600000000000 1428740 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": 968923, "vin": [ { "gen": { "height": 968913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c1fa09b56842a6e4548f55a55a10a83881065a16dc7ca49cd92d5e7916cf30b" } } ], "extra": [ 1, 2, 31, 158, 77, 6, 167, 181, 114, 82, 112, 96, 18, 212, 217, 138, 247, 54, 253, 42, 57, 202, 69, 250, 226, 46, 0, 12, 169, 150, 159, 130, 116, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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