← previous blocknext block →recent activity
Analyzing
Block #107,651,488
19 transactions · 18 stateful · 2026-09-24 16:11:23 UTC
Parallelism
68/100
Blocked
44%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,651,488 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
9w010w111w212w213w314w315w417w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x508174fb…94d2
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x097cee83…0878
0x34b655…2a6f
4 touches
1 conflict
0x1393df1d…afbd
0x34b655…2a6f
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x3324275f…6ef4
0x34b655…2a6f
4 touches
1 conflict
0x3ff9db2e…22f6
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
6 conflicts on slot 0x508174fbc3…8094d2
Audit this contract →
← previous block·next block →recent activity