Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6e91c4b095d8cacd0c9f867a9d91f4c11eb996d1ce69689df0a209b027b085d

Tx prefix hash: 654d7ad117abbf72bce60837376d6eff2118ac352b7d9db621403d78e5211f64
Tx public key: 10cc9d72d4a16831b25fbd1cf5bba3412d99fd4bd1c1378470656c655015057c
Timestamp: 1737105983 Timestamp [UCT]: 2025-01-17 09:26:23 Age [y:d:h:m:s]: 00:152:13:22:29
Block: 1199224 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108729 RingCT/type: yes/0
Extra: 0110cc9d72d4a16831b25fbd1cf5bba3412d99fd4bd1c1378470656c655015057c021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 033af694f9aef22db5515e0de01b4b556cbf65af8633ba796c6fbe7f593a1ec9 0.600000000000 1685853 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": 1199234, "vin": [ { "gen": { "height": 1199224 } } ], "vout": [ { "amount": 600000000, "target": { "key": "033af694f9aef22db5515e0de01b4b556cbf65af8633ba796c6fbe7f593a1ec9" } } ], "extra": [ 1, 16, 204, 157, 114, 212, 161, 104, 49, 178, 95, 189, 28, 245, 187, 163, 65, 45, 153, 253, 75, 209, 193, 55, 132, 112, 101, 108, 101, 80, 21, 5, 124, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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