Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a78d4a943a5c3f9c4737cea8e09e82f34a0d09439d7f5d8c467861c3738e4bdf

Tx prefix hash: 0eaa806c7471a84a2eaab99b9c5c0c5d9aa03c65b4287b1dff4cbbf3a1c71301
Tx public key: 4aff778f65f83ccf63bf311a8c39c04b1a154cb4f663bf6a5e8fc7c84729783c
Timestamp: 1727852767 Timestamp [UCT]: 2024-10-02 07:06:07 Age [y:d:h:m:s]: 00:112:13:43:58
Block: 1122664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80435 RingCT/type: yes/0
Extra: 014aff778f65f83ccf63bf311a8c39c04b1a154cb4f663bf6a5e8fc7c84729783c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bd074bb764cf5811b988282183243159b4f0fcc00cf8c78e844026214fa4b73 0.600000000000 1605149 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": 1122674, "vin": [ { "gen": { "height": 1122664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bd074bb764cf5811b988282183243159b4f0fcc00cf8c78e844026214fa4b73" } } ], "extra": [ 1, 74, 255, 119, 143, 101, 248, 60, 207, 99, 191, 49, 26, 140, 57, 192, 75, 26, 21, 76, 180, 246, 99, 191, 106, 94, 143, 199, 200, 71, 41, 120, 60, 2, 17, 0, 0, 0, 5, 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