← previous blocknext block →recent activity
Analyzing
Block #101,682,049
23 transactions · 19 stateful · 2026-09-03 18:08:04 UTC
Parallelism
74/100
Blocked
32%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,682,049 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w19w110w214w019w320w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3fb3f2e2…fef3
0x34b655…2a6f
4 touches
1 conflict
0x4f3cc09a…2804
0x34b655…2a6f
4 touches
1 conflict
0x582cac9c…2571
0x34b655…2a6f
4 touches
1 conflict
0x60f8746d…b3d9
0x34b655…2a6f
4 touches
1 conflict
0x70f836c8…cf6d
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity