← previous blocknext block →recent activity
Analyzing
Block #108,605,202
19 transactions · 19 stateful · 2026-09-28 00:13:03 UTC
Parallelism
79/100
Blocked
32%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,605,202 · 19 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
1w02w13w07w110w213w215w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4646dd5…0b8e
0x34b655…2a6f
6 touches
3 conflicts
0xc3306f42…9856
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xecff7c35…1b43
0x34b655…2a6f
4 touches
1 conflict
0x8217591f…c1b9
0x34b655…2a6f
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
3 conflicts on slot 0xc4646dd579…610b8e
Audit this contract →
← previous block·next block →recent activity