← previous blocknext block →recent activity
Analyzing
Block #102,208,179
10 transactions · 10 stateful · 2026-09-05 14:27:10 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,208,179 · 10 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
5w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7dd96c96…7335
0x34b655…2a6f
4 touches
1 conflict
0xdbadf6b0…43b2
0x33176b…e078
2 touches
0 conflicts
0x00f6a8a7…0e6e
0x34b655…2a6f
2 touches
0 conflicts
0x20e4fb89…ed25
0x34b655…2a6f
2 touches
0 conflicts
0x3d13406e…eff1
0x34b655…2a6f
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
3 conflicts on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity