Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7d800d8c16244b4f4fe2c54a1705b962ebd489f64e7a8f2d57bca9da3e63822

Tx prefix hash: b2bd055470d58d583dfc814c134c8a750b9d5bd5728fbcfa0ea3e83f4df83afb
Tx public key: 8ec749d6fb401a5716aa28a9051c5766da0acdb45c29e84822c535a0ca16d2ab
Timestamp: 1728191480 Timestamp [UCT]: 2024-10-06 05:11:20 Age [y:d:h:m:s]: 00:049:05:27:04
Block: 1125472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35155 RingCT/type: yes/0
Extra: 018ec749d6fb401a5716aa28a9051c5766da0acdb45c29e84822c535a0ca16d2ab02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30a2c11ef4b5c4eb0f09cf4e71d53ae1dbd88ff3b2e87d7a2a07c81b8b924532 0.600000000000 1608221 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": 1125482, "vin": [ { "gen": { "height": 1125472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30a2c11ef4b5c4eb0f09cf4e71d53ae1dbd88ff3b2e87d7a2a07c81b8b924532" } } ], "extra": [ 1, 142, 199, 73, 214, 251, 64, 26, 87, 22, 170, 40, 169, 5, 28, 87, 102, 218, 10, 205, 180, 92, 41, 232, 72, 34, 197, 53, 160, 202, 22, 210, 171, 2, 17, 0, 0, 0, 10, 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