← previous blocknext block →recent activity
Analyzing
Block #108,515,592
19 transactions · 19 stateful · 2026-09-27 16:41:48 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,515,592 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w18w29w314w015w117w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
6 touches
3 conflicts
0xfa2527aa…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0xfadc118d…5d64
0x34b655…2a6f
6 touches
3 conflicts
0x2a8bc05a…0464
0x37db7f…ec7b
6 touches
3 conflicts
0xa93fef74…94b3
0x37db7f…ec7b
6 touches
3 conflicts
0xdbcc4ab8…2aba
0x37db7f…ec7b
6 touches
3 conflicts
0x085df2c1…305a
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