Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af84e981c7ac64f8218eebcbe8dc01d7815e57b912854632ac7124184ed2d5e0

Tx prefix hash: fe3ba3f195ebd0fa9a8d6fa85f5e650591f354944868a7f3a876ba30d3315f15
Tx public key: 3c0ecf1cd0fb8d0d110c74054af76cc1e6674a4fa1efe70e0fa553893c671870
Timestamp: 1712779555 Timestamp [UCT]: 2024-04-10 20:05:55 Age [y:d:h:m:s]: 00:363:04:52:45
Block: 997669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259686 RingCT/type: yes/0
Extra: 013c0ecf1cd0fb8d0d110c74054af76cc1e6674a4fa1efe70e0fa553893c6718700211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97b76f11efcaecd90aa079e536f65213784007e781c3b0c1af55546593d91e3c 0.600000000000 1458103 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": 997679, "vin": [ { "gen": { "height": 997669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97b76f11efcaecd90aa079e536f65213784007e781c3b0c1af55546593d91e3c" } } ], "extra": [ 1, 60, 14, 207, 28, 208, 251, 141, 13, 17, 12, 116, 5, 74, 247, 108, 193, 230, 103, 74, 79, 161, 239, 231, 14, 15, 165, 83, 137, 60, 103, 24, 112, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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