Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3fa51fb18fd01db9b86f7797629568f275ac46bdd4b60ff792b163944e76b8a

Tx prefix hash: 9f6e5e9e31fb3173ccfe278bb3d340185577e12f3c1d84f31e4c2d18c7f366e1
Tx public key: e35459afba2438b99d0038284fa083df39c2c87b343fbe8bbc7962857e99c5e6
Timestamp: 1722848384 Timestamp [UCT]: 2024-08-05 08:59:44 Age [y:d:h:m:s]: 00:111:13:38:21
Block: 1081165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79827 RingCT/type: yes/0
Extra: 01e35459afba2438b99d0038284fa083df39c2c87b343fbe8bbc7962857e99c5e6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e54cc70051d12c34b968a2c2e82cd40d24db237449445836afdece73a447e3f 0.600000000000 1554808 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": 1081175, "vin": [ { "gen": { "height": 1081165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e54cc70051d12c34b968a2c2e82cd40d24db237449445836afdece73a447e3f" } } ], "extra": [ 1, 227, 84, 89, 175, 186, 36, 56, 185, 157, 0, 56, 40, 79, 160, 131, 223, 57, 194, 200, 123, 52, 63, 190, 139, 188, 121, 98, 133, 126, 153, 197, 230, 2, 17, 0, 0, 0, 5, 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