← previous blocknext block →recent activity
Analyzing
Block #101,956,485
21 transactions · 17 stateful · 2026-09-04 17:11:16 UTC
Parallelism
76/100
Blocked
24%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,956,485 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w110w217w319w020w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0c6a407c…2b73
0x34b655…2a6f
4 touches
1 conflict
0x14229360…d854
0x34b655…2a6f
4 touches
1 conflict
0x14690632…e9a5
0x34b655…2a6f
4 touches
1 conflict
0x1a693e8a…2480
0x34b655…2a6f
4 touches
1 conflict
0x1dbe3b2c…d159
0x34b655…2a6f
4 touches
1 conflict
0x2d02f869…1f83
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity