← previous blocknext block →recent activity
Analyzing
Block #108,602,930
22 transactions · 19 stateful · 2026-09-28 00:01:37 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,602,930 · 22 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
1w02w13w04w15w111w012w013w114w215w316w417w019w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c2fc330…0091
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0x1bc47ad8…a338
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
8 touches
6 conflicts
0x1e65a966…15e1
0x34b655…2a6f
6 touches
3 conflicts
0x17a7f697…dcb7
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x2bfa532a…1d25
0x34b655…2a6f
4 touches
1 conflict
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 0x9c2fc33042…7d0091
Audit this contract →
← previous block·next block →recent activity