Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0740b5f787878997bae9211062fee00a3a9e26adf8a2077a6f0e92e14e58d77

Tx prefix hash: 725ecc9da82380f5abb8880d2d789a10897ed945a2f2aa6b5625959de6db9583
Tx public key: cbf5baa239fe53675b8d38b763e3f42520b934fae78b6d1526545f2acf71a09b
Timestamp: 1718862874 Timestamp [UCT]: 2024-06-20 05:54:34 Age [y:d:h:m:s]: 00:205:19:01:36
Block: 1048130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147264 RingCT/type: yes/0
Extra: 01cbf5baa239fe53675b8d38b763e3f42520b934fae78b6d1526545f2acf71a09b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68eada54f4f5b100124be24e27a227b4c9045093c485b29efbb3ecf70e7b9833 0.600000000000 1518133 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": 1048140, "vin": [ { "gen": { "height": 1048130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68eada54f4f5b100124be24e27a227b4c9045093c485b29efbb3ecf70e7b9833" } } ], "extra": [ 1, 203, 245, 186, 162, 57, 254, 83, 103, 91, 141, 56, 183, 99, 227, 244, 37, 32, 185, 52, 250, 231, 139, 109, 21, 38, 84, 95, 42, 207, 113, 160, 155, 2, 17, 0, 0, 0, 2, 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