← previous blocknext block →recent activity
Analyzing
Block #108,610,368
21 transactions · 19 stateful · 2026-09-28 00:39:04 UTC
Parallelism
67/100
Blocked
37%
Avg conflicts / tx
0.62
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #108,610,368 · 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
6w07w18w211w313w015w016w118w419w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x366a19b0…f065
0x34b655…2a6f
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
6 touches
3 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0xdbcc4ab8…2aba
0x37db7f…ec7b
6 touches
3 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x59a54ff4…d21b
0x34b655…2a6f
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity