← previous blocknext block →recent activity
Analyzing
Block #107,823,400
21 transactions · 15 stateful · 2026-09-25 06:38:00 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,823,400 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w18w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdd70c3e1…061b
0x34b655…2a6f
6 touches
3 conflicts
0x91220b8f…7a08
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xae41dd26…b6a3
0xd32edf…ff58
5 touches
3 conflicts
0x845ec8b0…c1af
0x34b655…2a6f
4 touches
1 conflict
0xa7ba83b5…d0a8
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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 0xdd70c3e1f6…22061b
Audit this contract →
← previous block·next block →recent activity