Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c3ee2d12eeb6ac9f25ea50174b50b7bbed0b9306e19473dea7e79e46c2b41ba

Tx prefix hash: 5b892c9091c33fcd1b26d4ef92ffd210c93b6f903569309f8171fbd6659b976b
Tx public key: a17a5aec9fc2819f5d987ae9104d7a92d93df023cc95c6960c54fe726526e31e
Timestamp: 1714080885 Timestamp [UCT]: 2024-04-25 21:34:45 Age [y:d:h:m:s]: 00:250:15:26:52
Block: 1008471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179420 RingCT/type: yes/0
Extra: 01a17a5aec9fc2819f5d987ae9104d7a92d93df023cc95c6960c54fe726526e31e02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06f61b12d30e04a25d7543ca8be78cf2a486489a756aff6faf44ece92e568fa1 0.600000000000 1469941 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": 1008481, "vin": [ { "gen": { "height": 1008471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06f61b12d30e04a25d7543ca8be78cf2a486489a756aff6faf44ece92e568fa1" } } ], "extra": [ 1, 161, 122, 90, 236, 159, 194, 129, 159, 93, 152, 122, 233, 16, 77, 122, 146, 217, 61, 240, 35, 204, 149, 198, 150, 12, 84, 254, 114, 101, 38, 227, 30, 2, 17, 0, 0, 0, 2, 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