Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 782dcdce79847e52eddf1900eaf5750d99bcfb68ef796dc0d8b8cf7b62a7e221

Tx prefix hash: 5126e36a12870743777217a9671522c32f7bbc2ca02acaaf0fd9ef2b14adde17
Tx public key: 4d98ffbd0f01fa2b972c3fb2f3f47c7b07b359763a4486a086a1ce62a069d65e
Timestamp: 1760742787 Timestamp [UCT]: 2025-10-17 23:13:07 Age [y:d:h:m:s]: 00:070:07:50:50
Block: 1392230 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 50338 RingCT/type: yes/0
Extra: 014d98ffbd0f01fa2b972c3fb2f3f47c7b07b359763a4486a086a1ce62a069d65e0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 270f1457dca7026a268872c9a4c27710da820690ee6f43c0033007e4579a5415 0.600000000000 1880481 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": 1392240, "vin": [ { "gen": { "height": 1392230 } } ], "vout": [ { "amount": 600000000, "target": { "key": "270f1457dca7026a268872c9a4c27710da820690ee6f43c0033007e4579a5415" } } ], "extra": [ 1, 77, 152, 255, 189, 15, 1, 250, 43, 151, 44, 63, 178, 243, 244, 124, 123, 7, 179, 89, 118, 58, 68, 134, 160, 134, 161, 206, 98, 160, 105, 214, 94, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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