Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f96bf88875c9b35b5d2a485812bc2386b5bbcbbed2e97b4c70442d6a682ff42

Tx prefix hash: 0142d703891bf943c233b9610c849c4129be9755c47d63ccc015ce26e4ef1a42
Tx public key: f1a95b13ceb498eaa0a5ed7fdd97500dfa8e486a6fa1322a9638e8a8df109058
Timestamp: 1763614889 Timestamp [UCT]: 2025-11-20 05:01:29 Age [y:d:h:m:s]: 00:044:07:51:40
Block: 1416021 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31738 RingCT/type: yes/0
Extra: 01f1a95b13ceb498eaa0a5ed7fdd97500dfa8e486a6fa1322a9638e8a8df10905802110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a101647c678baf2a2e3bcf878da94a6c3c5dcf567cb414d3f00c2acd676a708 0.600000000000 1904540 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": 1416031, "vin": [ { "gen": { "height": 1416021 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a101647c678baf2a2e3bcf878da94a6c3c5dcf567cb414d3f00c2acd676a708" } } ], "extra": [ 1, 241, 169, 91, 19, 206, 180, 152, 234, 160, 165, 237, 127, 221, 151, 80, 13, 250, 142, 72, 106, 111, 161, 50, 42, 150, 56, 232, 168, 223, 16, 144, 88, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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