← previous blocknext block →recent activity
Analyzing
Block #107,816,374
18 transactions · 16 stateful · 2026-09-25 06:02:38 UTC
Parallelism
72/100
Blocked
31%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,816,374 · 18 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
1w02w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x98a5aa5c…77c9
0x34b655…2a6f
6 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
6 touches
3 conflicts
0xd53220ed…473b
0x1b6862…e19c
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0x2b856d86…7988
0x34b655…2a6f
4 touches
1 conflict
0x301e1c77…9e30
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 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity