← previous blocknext block →recent activity
Analyzing
Block #107,847,689
26 transactions · 25 stateful · 2026-09-25 08:40:15 UTC
Parallelism
77/100
Blocked
32%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #107,847,689 · 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
5w010w013w014w115w216w317w418w519w120w221w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54e6d2a8…ec22
0x34b655…2a6f
8 touches
6 conflicts
0xa174e283…e695
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x14fe1598…d0ba
0x34b655…2a6f
6 touches
3 conflicts
0x921a58d1…db22
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x3750b746…5a9e
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 0x54e6d2a8dc…74ec22
Audit this contract →
← previous block·next block →recent activity