← previous blocknext block →recent activity
Analyzing
Block #107,824,379
19 transactions · 17 stateful · 2026-09-25 06:42:55 UTC
Parallelism
58/100
Blocked
53%
Avg conflicts / tx
1.26
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,824,379 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w110w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66fc0764…05fd
0x34b655…2a6f
12 touches
15 conflicts
0xc2883066…14a6
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0xd18a8dca…4530
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
15 conflicts on slot 0x66fc076467…c305fd
Audit this contract →
← previous block·next block →recent activity