Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f747f7a06d77c920a60565e4c138e8ea6d267da9822d015416511dc82fe5bd26

Tx prefix hash: dd5b855b513654edbd9afba9bfb6a46ee7236d91eca9ad2d8a07f3392607a693
Tx public key: 639299baf3bf012ab7f417986a0297c74d19336ff9ae59f402c545cc11996a9c
Timestamp: 1747349411 Timestamp [UCT]: 2025-05-15 22:50:11 Age [y:d:h:m:s]: 00:259:04:58:30
Block: 1283751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182888 RingCT/type: yes/0
Extra: 01639299baf3bf012ab7f417986a0297c74d19336ff9ae59f402c545cc11996a9c02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82a9e11fcf62c4160031ebf4bdc60d6c4ca3c47e25e3f6a309b7db91e65f0f1f 0.600000000000 1771170 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": 1283761, "vin": [ { "gen": { "height": 1283751 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82a9e11fcf62c4160031ebf4bdc60d6c4ca3c47e25e3f6a309b7db91e65f0f1f" } } ], "extra": [ 1, 99, 146, 153, 186, 243, 191, 1, 42, 183, 244, 23, 152, 106, 2, 151, 199, 77, 25, 51, 111, 249, 174, 89, 244, 2, 197, 69, 204, 17, 153, 106, 156, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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