Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af4f01f48fc8461084ccb7377f1724961aa8e4ec6e86a15855b91cfcb0bdff00

Tx prefix hash: 575b08e63e5af79eba91315a1bca64767ac27412251f0c297444e051557422bd
Tx public key: 411af436efc534ad7d44df0edcfbf1d41f3b96bae1dc8f59b91885e6ae8aac56
Timestamp: 1717702122 Timestamp [UCT]: 2024-06-06 19:28:42 Age [y:d:h:m:s]: 00:282:12:14:27
Block: 1038510 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201901 RingCT/type: yes/0
Extra: 01411af436efc534ad7d44df0edcfbf1d41f3b96bae1dc8f59b91885e6ae8aac5602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b290d235dee4130f2b0e4f329e28ebbbf07c9daba31a53ae0f27c7b316f5ede 0.600000000000 1507071 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": 1038520, "vin": [ { "gen": { "height": 1038510 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b290d235dee4130f2b0e4f329e28ebbbf07c9daba31a53ae0f27c7b316f5ede" } } ], "extra": [ 1, 65, 26, 244, 54, 239, 197, 52, 173, 125, 68, 223, 14, 220, 251, 241, 212, 31, 59, 150, 186, 225, 220, 143, 89, 185, 24, 133, 230, 174, 138, 172, 86, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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