← previous blocknext block →recent activity
Analyzing
Block #107,823,512
18 transactions · 17 stateful · 2026-09-25 06:38:34 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
1.22
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #107,823,512 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w08w39w110w211w312w413w514w616w017w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
10 touches
10 conflicts
0x7ed4080f…0f62
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x9b334941…fde1
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
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 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity