Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec576cca23d86b4f13b245878e0bd9e76f9e040598c5f17cc71c72b6ab2313ce

Tx prefix hash: 21a8c2ce3ac9dd8ceb40f0a4c30cc5ae4eaa00d6bf0ef55b071302ab57cc8192
Tx public key: 65c3961dece6c88de05507f5c11bcbcee775e4e2caa10700146358d42708a3d1
Timestamp: 1722728706 Timestamp [UCT]: 2024-08-03 23:45:06 Age [y:d:h:m:s]: 00:296:22:13:08
Block: 1080175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212150 RingCT/type: yes/0
Extra: 0165c3961dece6c88de05507f5c11bcbcee775e4e2caa10700146358d42708a3d1021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df018a7e7ea57e5a56d4028d9be8a55eef8b5d422a9b45a470ccc96d19d6d542 0.600000000000 1553436 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": 1080185, "vin": [ { "gen": { "height": 1080175 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df018a7e7ea57e5a56d4028d9be8a55eef8b5d422a9b45a470ccc96d19d6d542" } } ], "extra": [ 1, 101, 195, 150, 29, 236, 230, 200, 141, 224, 85, 7, 245, 193, 27, 203, 206, 231, 117, 228, 226, 202, 161, 7, 0, 20, 99, 88, 212, 39, 8, 163, 209, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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