← previous blocknext block →recent activity
Analyzing
Block #108,610,637
19 transactions · 18 stateful · 2026-09-28 00:40:25 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,610,637 · 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
2w03w15w16w27w29w311w412w213w317w018w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa93fef74…94b3
0x37db7f…ec7b
6 touches
3 conflicts
0xdbcc4ab8…2aba
0x37db7f…ec7b
6 touches
3 conflicts
0xe3e67fe3…e754
0x37db7f…ec7b
6 touches
3 conflicts
0x5164ab0e…01e1
0xc8689a…ee79
6 touches
3 conflicts
0x3643741b…109c
0x34b655…2a6f
6 touches
3 conflicts
0x366a19b0…f065
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