Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 024a48b4153d75007feb8ce3a0d615051c11cd9c1fc2b05766fe6809eeabf31e

Tx prefix hash: 32876787d9d6d12f8b93c4d3c4432d886392c55e50d7cdbcd5787562d692817b
Tx public key: e6adf7a1bb7738e37196ef42a921bae718140fca1fac2694dd29d4a2dfa8c06f
Timestamp: 1724769226 Timestamp [UCT]: 2024-08-27 14:33:46 Age [y:d:h:m:s]: 00:225:05:51:43
Block: 1097091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160835 RingCT/type: yes/0
Extra: 01e6adf7a1bb7738e37196ef42a921bae718140fca1fac2694dd29d4a2dfa8c06f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a7e9f0d5c7be637dbfaeb34a89b32162c7fa99940329845ddd60fc9d04a8a7b 0.600000000000 1572386 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": 1097101, "vin": [ { "gen": { "height": 1097091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a7e9f0d5c7be637dbfaeb34a89b32162c7fa99940329845ddd60fc9d04a8a7b" } } ], "extra": [ 1, 230, 173, 247, 161, 187, 119, 56, 227, 113, 150, 239, 66, 169, 33, 186, 231, 24, 20, 15, 202, 31, 172, 38, 148, 221, 41, 212, 162, 223, 168, 192, 111, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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