Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4a0eb00fa42c390c5f54549c2531d5af395586f49cde5d38254a87e6a50ef26

Tx prefix hash: c3aae28818793671efc3b29f01ecd30e0c1905646100360dea27919f47f4469a
Tx public key: 27fb36d7156aa45a4f7443a0b56495f808fbc13d94b4b2f0bcf2bfae5070811d
Timestamp: 1722768658 Timestamp [UCT]: 2024-08-04 10:50:58 Age [y:d:h:m:s]: 00:247:14:56:00
Block: 1080508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176872 RingCT/type: yes/0
Extra: 0127fb36d7156aa45a4f7443a0b56495f808fbc13d94b4b2f0bcf2bfae5070811d021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5233be03db7beb3b172ddf617ffa0332b9a93043431748c9cc4a9c466a38eab1 0.600000000000 1553893 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": 1080518, "vin": [ { "gen": { "height": 1080508 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5233be03db7beb3b172ddf617ffa0332b9a93043431748c9cc4a9c466a38eab1" } } ], "extra": [ 1, 39, 251, 54, 215, 21, 106, 164, 90, 79, 116, 67, 160, 181, 100, 149, 248, 8, 251, 193, 61, 148, 180, 178, 240, 188, 242, 191, 174, 80, 112, 129, 29, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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