← previous blocknext block →recent activity
Analyzing
Block #96,143,110
10 transactions · 8 stateful · 2026-08-15 07:24:37 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,143,110 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0cc22f4…af33
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6571
0x34b655…2a6f
4 touches
1 conflict
0x40a9339c…6572
0x34b655…2a6f
4 touches
1 conflict
0x6bb75770…8886
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab0
0x34b655…2a6f
4 touches
1 conflict
0xa4e9800f…4ab1
0x34b655…2a6f
4 touches
1 conflict
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 0xb0cc22f4c2…33af33
Audit this contract →
← previous block·next block →recent activity