← previous blocknext block →recent activity
Analyzing
Block #108,610,192
27 transactions · 26 stateful · 2026-09-28 00:38:11 UTC
Parallelism
67/100
Blocked
54%
Avg conflicts / tx
1.26
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #108,610,192 · 27 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w28w09w110w111w212w313w414w515w616w725w726w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42522e76…2592
0x34b655…2a6f
12 touches
15 conflicts
0xc1da8f73…484c
0x34b655…2a6f
10 touches
10 conflicts
0x831a5ce7…722c
0x34b655…2a6f
8 touches
6 conflicts
0xf06fce24…887d
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x17b1b108…8e96
0x34b655…2a6f
6 touches
3 conflicts
0xcd92ceb8…b9d2
0xa6afd3…d132
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
15 conflicts on slot 0x42522e76ce…082592
Audit this contract →
← previous block·next block →recent activity