← previous blocknext block →recent activity
Analyzing
Block #106,382,997
13 transactions · 13 stateful · 2026-09-20 05:44:36 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,382,997 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w18w29w312w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02fa927d…6468
0x34b655…2a6f
8 touches
6 conflicts
0xf171f918…801d
0x34b655…2a6f
4 touches
1 conflict
0x4265984a…a7d2
0x34b655…2a6f
4 touches
1 conflict
0x41ace351…c970
0x34b655…2a6f
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
2 touches
0 conflicts
0x0ca39818…c6d0
0x34b655…2a6f
2 touches
0 conflicts
0x30c5329c…711c
0x34b655…2a6f
2 touches
0 conflicts
0x3786a2d7…4c21
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
6 conflicts on slot 0x02fa927dec…786468
Audit this contract →
← previous block·next block →recent activity