← previous blocknext block →recent activity
Analyzing
Block #107,630,188
26 transactions · 24 stateful · 2026-09-24 14:24:02 UTC
Parallelism
77/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,630,188 · 26 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
1w02w03w16w08w113w017w018w119w220w321w422w524w025w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x503716b1…f16c
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0xaf4b5f6f…49cc
0x34b655…2a6f
6 touches
3 conflicts
0x42744667…0b8a
0x34b655…2a6f
6 touches
3 conflicts
0x178fe051…465a
0x34b655…2a6f
6 touches
3 conflicts
0xa0a8c7a5…3422
0x34b655…2a6f
4 touches
1 conflict
0xad2c92cc…9bcd
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