← previous blocknext block →recent activity
Analyzing
Block #108,609,998
21 transactions · 21 stateful · 2026-09-28 00:37:12 UTC
Parallelism
67/100
Blocked
52%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,609,998 · 21 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
1w02w13w24w36w110w011w112w213w314w215w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x31d88d27…7617
0x34b655…2a6f
10 touches
10 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x28e2f7c3…e848
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x93afca4c…b47f
0x1b6862…e19c
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 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 0x31d88d27c1…837617
Audit this contract →
← previous block·next block →recent activity