Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65b09c1f99e2d254745d33d60d45eb1e2e3eaa63efdea771af1d880d9ae7fb8e

Tx prefix hash: 4db1e9c5edd89ef79a0a357119b454071a4e8113c4115dbfb7fa07104a625797
Tx public key: adfb60b1322e839b60b333199fc2c99c7df3f0c489c163f572ce14ac81ae6756
Timestamp: 1734837144 Timestamp [UCT]: 2024-12-22 03:12:24 Age [y:d:h:m:s]: 00:096:04:43:15
Block: 1180480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68498 RingCT/type: yes/0
Extra: 01adfb60b1322e839b60b333199fc2c99c7df3f0c489c163f572ce14ac81ae6756021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e10a79af012fd4056fc1bad7ce5c9824595adde9f63fd7113aed465d69e4ded0 0.600000000000 1666891 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": 1180490, "vin": [ { "gen": { "height": 1180480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e10a79af012fd4056fc1bad7ce5c9824595adde9f63fd7113aed465d69e4ded0" } } ], "extra": [ 1, 173, 251, 96, 177, 50, 46, 131, 155, 96, 179, 51, 25, 159, 194, 201, 156, 125, 243, 240, 196, 137, 193, 99, 245, 114, 206, 20, 172, 129, 174, 103, 86, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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