Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7e51cd3f9dbed89e70739d43a581fffa027188ce3d37dba93d65b53706f619

Tx prefix hash: aaa53c7aa7772e89edee5091b2a0f2414b5f0cf0e9d8f96ad6ad2314eab9ab9a
Tx public key: e26bf51607dd60b35ce941a0d4713842ac30271ec1a0c4ef96fff1d353b4ea47
Timestamp: 1713714043 Timestamp [UCT]: 2024-04-21 15:40:43 Age [y:d:h:m:s]: 00:205:19:57:12
Block: 1005436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147355 RingCT/type: yes/0
Extra: 01e26bf51607dd60b35ce941a0d4713842ac30271ec1a0c4ef96fff1d353b4ea4702110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36a790710e0a83ac55e96410c95d8794f4f43110a1c9dce525b55f8db7317581 0.600000000000 1466120 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": 1005446, "vin": [ { "gen": { "height": 1005436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36a790710e0a83ac55e96410c95d8794f4f43110a1c9dce525b55f8db7317581" } } ], "extra": [ 1, 226, 107, 245, 22, 7, 221, 96, 179, 92, 233, 65, 160, 212, 113, 56, 66, 172, 48, 39, 30, 193, 160, 196, 239, 150, 255, 241, 211, 83, 180, 234, 71, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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