Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5364362f66e8e9bc8c7eee471f42b4efc75c7b7a6b439f91c6312f9f1493214e

Tx prefix hash: fae2f62d29753f2e56f09646b4ced51ed9de7b283c2e562867794d969a5481e8
Tx public key: 41a4f8949bd91a482164081089a925c7d8befcc9725ec6666eee03a42274a287
Timestamp: 1709658497 Timestamp [UCT]: 2024-03-05 17:08:17 Age [y:d:h:m:s]: 01:276:00:26:45
Block: 971826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 456019 RingCT/type: yes/0
Extra: 0141a4f8949bd91a482164081089a925c7d8befcc9725ec6666eee03a42274a2870211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ab53ee675a4c4ebb57b7db0454f68bc03b27b844e87573abefdaae8b27034b5 0.600000000000 1431729 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": 971836, "vin": [ { "gen": { "height": 971826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ab53ee675a4c4ebb57b7db0454f68bc03b27b844e87573abefdaae8b27034b5" } } ], "extra": [ 1, 65, 164, 248, 148, 155, 217, 26, 72, 33, 100, 8, 16, 137, 169, 37, 199, 216, 190, 252, 201, 114, 94, 198, 102, 110, 238, 3, 164, 34, 116, 162, 135, 2, 17, 0, 0, 0, 1, 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