← previous blocknext block →recent activity
Analyzing
Block #94,752,796
24 transactions · 17 stateful · 2026-08-10 10:35:24 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,752,796 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w013w014w115w216w320w121w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x160f117d…8e90
0x065c9d…c394
2 touches
0 conflicts
0x1a2e973b…ad43
0x065c9d…c394
2 touches
0 conflicts
0x21ce50e9…a246
0x065c9d…c394
2 touches
0 conflicts
0x31ccb69b…4ade
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity