← previous blocknext block →recent activity
Analyzing
Block #107,982,379
40 transactions · 29 stateful · 2026-09-25 19:58:17 UTC
Parallelism
88/100
Blocked
48%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #107,982,379 · 40 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
1w06w110w011w114w016w119w221w022w124w225w329w431w238w439w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x0f8047b9…1163
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0xcb45d9d6…cb82
0x1b6862…e19c
8 touches
6 conflicts
0x74e485b1…d380
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity