← previous blocknext block →recent activity
Analyzing
Block #108,512,001
21 transactions · 20 stateful · 2026-09-27 16:23:43 UTC
Parallelism
76/100
Blocked
60%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,512,001 · 21 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
1w02w13w29w110w211w312w313w414w215w316w418w019w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xedf736f2…633b
0x34b655…2a6f
8 touches
6 conflicts
0x1d9867ad…6d9a
0x34b655…2a6f
8 touches
6 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002d
0x1b6862…e19c
6 touches
3 conflicts
0xd53220ed…4739
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 0xedf736f262…b3633b
Audit this contract →
← previous block·next block →recent activity