Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c6f5b64c61cc83094d865d1ca7f237cbc6229441b8dac8f716d70e18e507a393

Tx prefix hash: 343839df4ffecc781f8d10680d15c267f927b110471f9a9df120211a2ee36e87
Tx public key: eeda2d2d5c5d7cb23a32ab32cad90c876ccfff15b294bf161d47850d739744ad
Timestamp: 1708142932 Timestamp [UCT]: 2024-02-17 04:08:52 Age [y:d:h:m:s]: 01:043:20:15:47
Block: 959251 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292369 RingCT/type: yes/0
Extra: 01eeda2d2d5c5d7cb23a32ab32cad90c876ccfff15b294bf161d47850d739744ad0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3aafbf6e37913d716f13c68eb35fb35395142911a2a91e4e19b574282ab38a6 0.600000000000 1418782 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": 959261, "vin": [ { "gen": { "height": 959251 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3aafbf6e37913d716f13c68eb35fb35395142911a2a91e4e19b574282ab38a6" } } ], "extra": [ 1, 238, 218, 45, 45, 92, 93, 124, 178, 58, 50, 171, 50, 202, 217, 12, 135, 108, 207, 255, 21, 178, 148, 191, 22, 29, 71, 133, 13, 115, 151, 68, 173, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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