Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c51297e06540448070af1cde0081b2023935cbc5f8ed3c8ef33fa6a6cee05456

Tx prefix hash: 99071eae1d5efaa6e527a71acea1b4ff41d6ed499e42812868252e9226f2365e
Tx public key: 6f26da44b9a21211052b654a5a27062415c7de3c81fea253be801acd0e638c44
Timestamp: 1742875187 Timestamp [UCT]: 2025-03-25 03:59:47 Age [y:d:h:m:s]: 00:311:16:28:43
Block: 1246710 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220421 RingCT/type: yes/0
Extra: 016f26da44b9a21211052b654a5a27062415c7de3c81fea253be801acd0e638c4402110000000324ff4ea1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bfa5c017f074e873d9cee9e4320d446102cfdac42041a60ef0fbfc932004356 0.600000000000 1733711 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": 1246720, "vin": [ { "gen": { "height": 1246710 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bfa5c017f074e873d9cee9e4320d446102cfdac42041a60ef0fbfc932004356" } } ], "extra": [ 1, 111, 38, 218, 68, 185, 162, 18, 17, 5, 43, 101, 74, 90, 39, 6, 36, 21, 199, 222, 60, 129, 254, 162, 83, 190, 128, 26, 205, 14, 99, 140, 68, 2, 17, 0, 0, 0, 3, 36, 255, 78, 161, 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