← previous blocknext block →recent activity
Analyzing
Block #105,618,500
20 transactions · 19 stateful · 2026-09-17 13:34:27 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,618,500 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w19w210w211w312w413w314w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2a274b47…ed5a
0x34b655…2a6f
8 touches
6 conflicts
0xcadd9a74…8bb7
0x34b655…2a6f
8 touches
6 conflicts
0xef8df0d1…b43f
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x0efc210e…70ab
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x6ca0994e…02ef
0x34b655…2a6f
6 touches
3 conflicts
0x95d42ebe…2a65
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
6 conflicts on slot 0x2a274b47a7…97ed5a
Audit this contract →
← previous block·next block →recent activity