← previous blocknext block →recent activity
Analyzing
Block #106,548,966
9 transactions · 7 stateful · 2026-09-20 19:39:57 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,548,966 · 9 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
5w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5e9b4cfc…4a39
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xd62f3741…b903
0x34b655…2a6f
4 touches
1 conflict
0x4842cd53…cbd5
0x34b655…2a6f
4 touches
1 conflict
0x94e7f277…471b
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
2 touches
0 conflicts
0x3837cfeb…840b
0x34b655…2a6f
2 touches
0 conflicts
0x4b6721e8…dd37
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 0x5e9b4cfc2e…294a39
Audit this contract →
← previous block·next block →recent activity