Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50341fadbb5f67a482dccdcf23c5e3cd5f2cb3f8ea80e99726832da3fe72004c

Tx prefix hash: 579f818bf526cfb852709b750f3dd66c4486869e0048e4902205b7ab77c28263
Tx public key: f50b3ee01276b5d47d0f7ea33637f7113401ce99327a9f901bcd921755a1c431
Timestamp: 1753927214 Timestamp [UCT]: 2025-07-31 02:00:14 Age [y:d:h:m:s]: 00:112:20:21:43
Block: 1337033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79496 RingCT/type: yes/0
Extra: 01f50b3ee01276b5d47d0f7ea33637f7113401ce99327a9f901bcd921755a1c43102110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44a29604d16d87650f4ecc05fcfb4b25e05f935b25cf9271b2255897b5c9a08 0.600000000000 1824836 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": 1337043, "vin": [ { "gen": { "height": 1337033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44a29604d16d87650f4ecc05fcfb4b25e05f935b25cf9271b2255897b5c9a08" } } ], "extra": [ 1, 245, 11, 62, 224, 18, 118, 181, 212, 125, 15, 126, 163, 54, 55, 247, 17, 52, 1, 206, 153, 50, 122, 159, 144, 27, 205, 146, 23, 85, 161, 196, 49, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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