← previous blocknext block →recent activity
Analyzing
Block #107,816,043
25 transactions · 24 stateful · 2026-09-25 06:00:58 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,816,043 · 25 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
1w010w011w112w213w314w415w521w022w123w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc7679110…572d
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x0b3f5b25…7d77
0x34b655…2a6f
6 touches
3 conflicts
0x2119060f…0f05
0x34b655…2a6f
6 touches
3 conflicts
0x2328941c…84d3
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2bd71786…2d83
0x34b655…2a6f
6 touches
3 conflicts
0x7c5c8608…021d
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 0xc7679110cf…22572d
Audit this contract →
← previous block·next block →recent activity