← previous blocknext block →recent activity
Analyzing
Block #107,640,448
26 transactions · 21 stateful · 2026-09-24 15:15:43 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #107,640,448 · 26 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
1w02w16w07w18w016w017w018w119w221w122w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004b
0x80c745…7210
4 touches
1 conflict
0x776a32db…621b
0x34b655…2a6f
4 touches
1 conflict
0x972a1622…f9a9
0x34b655…2a6f
4 touches
1 conflict
0x9b419d78…018b
0x34b655…2a6f
4 touches
1 conflict
0xc4c27b7f…ad59
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
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 0x49890ced8d…316f23
Audit this contract →
← previous block·next block →recent activity