← previous blocknext block →recent activity
Analyzing
Block #106,337,503
26 transactions · 24 stateful · 2026-09-20 01:55:38 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.85
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,337,503 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w08w112w213w314w315w116w418w020w023w224w125w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xac1228d4…f289
0x34b655…2a6f
6 touches
3 conflicts
0x0d72fcee…4b28
0x34b655…2a6f
4 touches
1 conflict
0x2a2896a0…2a0a
0x34b655…2a6f
4 touches
1 conflict
0x310a7246…2dcb
0x34b655…2a6f
4 touches
1 conflict
0x33145b09…268c
0x34b655…2a6f
4 touches
1 conflict
0x3fa1fac4…826c
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity