← previous blocknext block →recent activity
Analyzing
Block #107,816,869
18 transactions · 17 stateful · 2026-09-25 06:05:07 UTC
Parallelism
44/100
Blocked
59%
Avg conflicts / tx
1.5
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #107,816,869 · 18 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w29w310w411w512w613w714w815w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc95b4241…936c
0x34b655…2a6f
10 touches
10 conflicts
0xbdd97c21…e3d0
0x34b655…2a6f
10 touches
10 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x2029b74e…c206
0x34b655…2a6f
8 touches
6 conflicts
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0x588380ee…0a5c
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0xc95b424131…f5936c
Audit this contract →
← previous block·next block →recent activity