Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8aad1533855bf6d33ca331dcf41a8b481c76da399744b1268a4666976f76a64

Tx prefix hash: c868b7a00423a7b82ae8fc6d7a200badcd0e3bdd6602d2b50ec951d4dafee9d7
Tx public key: 05633432ff8f4c28b28743e79c03713a04e9945a7a6555fac34bf248a1c5a733
Timestamp: 1729674065 Timestamp [UCT]: 2024-10-23 09:01:05 Age [y:d:h:m:s]: 00:036:01:36:25
Block: 1137729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25767 RingCT/type: yes/0
Extra: 0105633432ff8f4c28b28743e79c03713a04e9945a7a6555fac34bf248a1c5a7330211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b59991f2e1935f4911158f2a7c389d04d6fa46f40c568894f25bc533de7e04db 0.600000000000 1621276 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": 1137739, "vin": [ { "gen": { "height": 1137729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b59991f2e1935f4911158f2a7c389d04d6fa46f40c568894f25bc533de7e04db" } } ], "extra": [ 1, 5, 99, 52, 50, 255, 143, 76, 40, 178, 135, 67, 231, 156, 3, 113, 58, 4, 233, 148, 90, 122, 101, 85, 250, 195, 75, 242, 72, 161, 197, 167, 51, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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