Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d32c13ba238479fc1050e42536805f01a900587ba4df4c3742af9e68050ede6e

Tx prefix hash: 214b9fd71446ed8f455b1b6078829f89000510f50b2a93c5e5272715e956c7a1
Tx public key: fbc76b3cd9fb6d0bb23f177c10a21f27b62488b00eefa1276e1191eff525cb1e
Timestamp: 1745118623 Timestamp [UCT]: 2025-04-20 03:10:23 Age [y:d:h:m:s]: 00:214:15:47:17
Block: 1265296 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151134 RingCT/type: yes/0
Extra: 01fbc76b3cd9fb6d0bb23f177c10a21f27b62488b00eefa1276e1191eff525cb1e02110000000adbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91616eb8da6f2b61ad2ebd43f9c41cda2fab4ca9c321a7340d6c9b8af3ab91cb 0.600000000000 1752501 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": 1265306, "vin": [ { "gen": { "height": 1265296 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91616eb8da6f2b61ad2ebd43f9c41cda2fab4ca9c321a7340d6c9b8af3ab91cb" } } ], "extra": [ 1, 251, 199, 107, 60, 217, 251, 109, 11, 178, 63, 23, 124, 16, 162, 31, 39, 182, 36, 136, 176, 14, 239, 161, 39, 110, 17, 145, 239, 245, 37, 203, 30, 2, 17, 0, 0, 0, 10, 219, 181, 113, 193, 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