← previous blocknext block →recent activity
Analyzing
Block #107,444,076
20 transactions · 18 stateful · 2026-09-23 22:46:42 UTC
Parallelism
80/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,444,076 · 20 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
1w02w13w05w16w27w08w111w112w213w218w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x550064a9…c4f2
0x34b655…2a6f
4 touches
1 conflict
0x5c1cc07a…b400
0x34b655…2a6f
4 touches
1 conflict
0x662d9b98…0f6b
0x34b655…2a6f
4 touches
1 conflict
0x9a1f2453…01b8
0x34b655…2a6f
4 touches
1 conflict
0xad862891…5d02
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 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity