← previous blocknext block →recent activity
Analyzing
Block #108,451,829
14 transactions · 11 stateful · 2026-09-27 11:20:49 UTC
Parallelism
71/100
Blocked
27%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,451,829 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w3
- 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
4 touches
1 conflict
0x71d2adcf…27bc
0x34b655…2a6f
4 touches
1 conflict
0x8d5914d7…8eba
0x34b655…2a6f
4 touches
1 conflict
0xbd24b5a5…4efa
0x34b655…2a6f
4 touches
1 conflict
0x2a8bc05a…0464
0x37db7f…ec7b
4 touches
1 conflict
0xa93fef74…94b3
0x37db7f…ec7b
4 touches
1 conflict
0xdbcc4ab8…2aba
0x37db7f…ec7b
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
6 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity