← previous blocknext block →recent activity
Analyzing
Block #108,575,175
13 transactions · 13 stateful · 2026-09-27 21:41:54 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,575,175 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb066c72c…87d2
0x34b655…2a6f
4 touches
1 conflict
0xd84ae63f…567b
0x34b655…2a6f
4 touches
1 conflict
0xaa3cf307…30e8
0x34b655…2a6f
4 touches
1 conflict
0x132b9de1…183b
0x34b655…2a6f
4 touches
1 conflict
0x213ee207…a151
0x34ae4d…3fc5
2 touches
0 conflicts
0x0215d8e5…68d5
0x34b655…2a6f
2 touches
0 conflicts
0x1876a569…4fb3
0x34b655…2a6f
2 touches
0 conflicts
0x3cb91dc8…c97d
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
1 conflict on slot 0xb066c72c02…d487d2
Audit this contract →
← previous block·next block →recent activity