Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 994825573fdf4bbf0f8894d162744a9ed6453f47c26752a61928ab4cedb5e886

Tx prefix hash: baa67a71e190f508d8f46af20fd71f63218e9cf049b16c4f59c6851041d1b592
Tx public key: d5e88d5acfa21b8d90bd39fde7453555fd3e02c64e870c80a5cc8bff263be1e0
Timestamp: 1723412499 Timestamp [UCT]: 2024-08-11 21:41:39 Age [y:d:h:m:s]: 00:290:20:09:00
Block: 1085846 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207790 RingCT/type: yes/0
Extra: 01d5e88d5acfa21b8d90bd39fde7453555fd3e02c64e870c80a5cc8bff263be1e0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05de41aca3ab0111198f21891b31a502667659f21de40f85b57035b9e28c451f 0.600000000000 1560437 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": 1085856, "vin": [ { "gen": { "height": 1085846 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05de41aca3ab0111198f21891b31a502667659f21de40f85b57035b9e28c451f" } } ], "extra": [ 1, 213, 232, 141, 90, 207, 162, 27, 141, 144, 189, 57, 253, 231, 69, 53, 85, 253, 62, 2, 198, 78, 135, 12, 128, 165, 204, 139, 255, 38, 59, 225, 224, 2, 17, 0, 0, 0, 2, 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