Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 044671f2096050dc7a3d65271c812fc95ce2abf3ee3c757c92b1c6b9fa09dbb5

Tx prefix hash: 17accc958c4ee662205ee8b9e17f49b274461c67918e9bb60c30631543ee1265
Tx public key: 13dd17d5b1d9c7cf0f381f796decba4cc15010bdc30685d75066fc7c29f8aa68
Timestamp: 1706501349 Timestamp [UCT]: 2024-01-29 04:09:09 Age [y:d:h:m:s]: 01:070:23:49:28
Block: 945622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311819 RingCT/type: yes/0
Extra: 0113dd17d5b1d9c7cf0f381f796decba4cc15010bdc30685d75066fc7c29f8aa6802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ea5c95b3bcd3e14c00a71df9406f67e8137694b69ef4e7d5597393d2f138150 0.600000000000 1403938 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": 945632, "vin": [ { "gen": { "height": 945622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ea5c95b3bcd3e14c00a71df9406f67e8137694b69ef4e7d5597393d2f138150" } } ], "extra": [ 1, 19, 221, 23, 213, 177, 217, 199, 207, 15, 56, 31, 121, 109, 236, 186, 76, 193, 80, 16, 189, 195, 6, 133, 215, 80, 102, 252, 124, 41, 248, 170, 104, 2, 17, 0, 0, 0, 5, 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