← previous blocknext block →recent activity
Analyzing
Block #107,839,084
24 transactions · 22 stateful · 2026-09-25 07:56:56 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #107,839,084 · 24 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
1w02w16w28w211w012w013w116w217w318w219w221w022w123w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbb96f8af…205f
0x34b655…2a6f
8 touches
6 conflicts
0x2d2d5513…1914
0x34b655…2a6f
8 touches
6 conflicts
0x3750b746…5a9e
0x34b655…2a6f
8 touches
6 conflicts
0x2328941c…84d3
0x34b655…2a6f
8 touches
6 conflicts
0x2ea475a4…f6c8
0xd32edf…ff58
7 touches
6 conflicts
0x607e2ee6…759c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
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 0xbb96f8afb0…6b205f
Audit this contract →
← previous block·next block →recent activity