Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fa70607afd419a3803acdc8fd28090ba624b6cae80b90199e1db27b3436c1bd

Tx prefix hash: efab983a79ffb026e5e083b7b8ac9d049e1c656d381ed7de1fca8da9f15dd9d0
Tx public key: 4bce96ff4b30abf69c1bfcd91be7da7ad5def37d0f81504b7765f552ea953740
Timestamp: 1751131980 Timestamp [UCT]: 2025-06-28 17:33:00 Age [y:d:h:m:s]: 00:144:14:46:03
Block: 1314665 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101449 RingCT/type: yes/0
Extra: 014bce96ff4b30abf69c1bfcd91be7da7ad5def37d0f81504b7765f552ea953740021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6fbbbc23e90e1ff7027f106bdaae6b0c93fec105303569239701fb041b3150c6 0.600000000000 1802316 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": 1314675, "vin": [ { "gen": { "height": 1314665 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6fbbbc23e90e1ff7027f106bdaae6b0c93fec105303569239701fb041b3150c6" } } ], "extra": [ 1, 75, 206, 150, 255, 75, 48, 171, 246, 156, 27, 252, 217, 27, 231, 218, 122, 213, 222, 243, 125, 15, 129, 80, 75, 119, 101, 245, 82, 234, 149, 55, 64, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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