← previous blocknext block →recent activity
Analyzing
Block #108,103,260
31 transactions · 28 stateful · 2026-09-26 06:06:34 UTC
Parallelism
81/100
Blocked
39%
Avg conflicts / tx
0.87
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,103,260 · 31 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
2w03w15w08w110w011w112w213w320w422w123w424w225w330w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xea02471d…1542
0x34b655…2a6f
12 touches
15 conflicts
0x451e482b…7e7d
0x34b655…2a6f
10 touches
10 conflicts
0x74e485b1…d380
0x34b655…2a6f
10 touches
10 conflicts
0x3643741b…109c
0x34b655…2a6f
8 touches
6 conflicts
0x3f152ba8…cea6
0x34b655…2a6f
8 touches
6 conflicts
0x45885570…ed97
0x34b655…2a6f
8 touches
6 conflicts
0x7b0297c7…8f17
0x34b655…2a6f
8 touches
6 conflicts
0x8d5914d7…8eba
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
15 conflicts on slot 0xea02471df2…601542
Audit this contract →
← previous block·next block →recent activity