Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c23963cbd2d3bfb4fa2747bbcbf7103d4b509cbcec840d84a0358f0d41edc1d

Tx prefix hash: 38ab33c950c37520d72e6aae7684a4f00264d8c95dac83a8f966d36e2bc76fb4
Tx public key: 87f98941871a057c560a300433b719da50a3a75d7ec24d085dc8fc7c81cb6995
Timestamp: 1761733419 Timestamp [UCT]: 2025-10-29 10:23:39 Age [y:d:h:m:s]: 00:059:17:45:55
Block: 1400433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42772 RingCT/type: yes/0
Extra: 0187f98941871a057c560a300433b719da50a3a75d7ec24d085dc8fc7c81cb699502110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3930784734e80c1a127f9e79a3ad29dd2adfbecae463fb81cd11e0023d9bc8a 0.600000000000 1888740 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": 1400443, "vin": [ { "gen": { "height": 1400433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3930784734e80c1a127f9e79a3ad29dd2adfbecae463fb81cd11e0023d9bc8a" } } ], "extra": [ 1, 135, 249, 137, 65, 135, 26, 5, 124, 86, 10, 48, 4, 51, 183, 25, 218, 80, 163, 167, 93, 126, 194, 77, 8, 93, 200, 252, 124, 129, 203, 105, 149, 2, 17, 0, 0, 0, 2, 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