← previous blocknext block →recent activity
Analyzing
Block #107,838,991
24 transactions · 22 stateful · 2026-09-25 07:56:27 UTC
Parallelism
79/100
Blocked
64%
Avg conflicts / tx
1.25
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,838,991 · 24 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
1w02w03w16w28w39w410w111w112w113w214w315w016w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0x25144f94…1854
0x34b655…2a6f
6 touches
3 conflicts
0xdcd07321…1c31
0x34b655…2a6f
6 touches
3 conflicts
0xa2c4d203…05b6
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x5786194a…9fb4
0xd32edf…ff58
5 touches
3 conflicts
0xcb45d9d6…cb87
0x1b6862…e19c
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity