Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12a50a138f4a46ba93e6b1b08e65d925e281236c043c29c4ce7d38b980cf3c54

Tx prefix hash: 62f9a10440e71ee3c67a9bc916b1eb3cc78e309ed75f0cc97b6e7a22183ce336
Tx public key: d515212622a986a1ff27e35a6c482a5744e5c0797148932df4992800cb9779ba
Timestamp: 1764826604 Timestamp [UCT]: 2025-12-04 05:36:44 Age [y:d:h:m:s]: 00:060:03:34:03
Block: 1426061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42883 RingCT/type: yes/0
Extra: 01d515212622a986a1ff27e35a6c482a5744e5c0797148932df4992800cb9779ba021100000007d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62e2c071a4f78c8d1914c421885a7c884ee6738af45b558e7a29bbc19d7948dd 0.600000000000 1914744 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": 1426071, "vin": [ { "gen": { "height": 1426061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62e2c071a4f78c8d1914c421885a7c884ee6738af45b558e7a29bbc19d7948dd" } } ], "extra": [ 1, 213, 21, 33, 38, 34, 169, 134, 161, 255, 39, 227, 90, 108, 72, 42, 87, 68, 229, 192, 121, 113, 72, 147, 45, 244, 153, 40, 0, 203, 151, 121, 186, 2, 17, 0, 0, 0, 7, 214, 225, 157, 124, 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