← previous blocknext block →recent activity
Analyzing
Block #108,351,450
29 transactions · 26 stateful · 2026-09-27 02:55:37 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #108,351,450 · 29 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
1w02w14w05w16w07w19w211w317w122w025w126w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcd5e68f…2a12
0x34b655…2a6f
10 touches
10 conflicts
0x23c8c8dd…7a42
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
8 touches
6 conflicts
0x5969523e…5191
0x34b655…2a6f
6 touches
3 conflicts
0x5ad5e6de…e7ad
0x34b655…2a6f
6 touches
3 conflicts
0x7006165a…df17
0x34b655…2a6f
6 touches
3 conflicts
0x76832384…dc5b
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
10 conflicts on slot 0xfcd5e68f28…382a12
Audit this contract →
← previous block·next block →recent activity