Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4efc795583ec7354cff9a92fe5221e5c5b24991d9d31404b66c24eb8184e0c1

Tx prefix hash: f502807ae47942f3bb618798a32bc4f2c322529743cd4ae186940127c51a373f
Tx public key: 0fc7e4829ccb0cb3e6ab0ef39b4f77e03359790cf46d583af802f2eaa0638547
Timestamp: 1736301010 Timestamp [UCT]: 2025-01-08 01:50:10 Age [y:d:h:m:s]: 00:160:02:21:01
Block: 1192559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114143 RingCT/type: yes/0
Extra: 010fc7e4829ccb0cb3e6ab0ef39b4f77e03359790cf46d583af802f2eaa06385470211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4241791d7c319f84675bc9fcd98efffaf7afa2149e9caa4407dcf1668beb780 0.600000000000 1679112 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": 1192569, "vin": [ { "gen": { "height": 1192559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4241791d7c319f84675bc9fcd98efffaf7afa2149e9caa4407dcf1668beb780" } } ], "extra": [ 1, 15, 199, 228, 130, 156, 203, 12, 179, 230, 171, 14, 243, 155, 79, 119, 224, 51, 89, 121, 12, 244, 109, 88, 58, 248, 2, 242, 234, 160, 99, 133, 71, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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