← previous blocknext block →recent activity
Analyzing
Block #107,848,263
24 transactions · 21 stateful · 2026-09-25 08:43:08 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
1.58
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #107,848,263 · 24 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
1w02w13w29w010w311w012w113w214w315w116w417w518w620w722w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xecff7c35…1b43
0x34b655…2a6f
14 touches
21 conflicts
0x232b0b19…d946
0x34b655…2a6f
12 touches
15 conflicts
0x31d88d27…7617
0x34b655…2a6f
12 touches
15 conflicts
0xd344088c…806f
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x8d47c9a4…f121
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
21 conflicts on slot 0xecff7c3510…111b43
Audit this contract →
← previous block·next block →recent activity