← previous blocknext block →recent activity
Analyzing
Block #108,672,146
10 transactions · 9 stateful · 2026-09-28 05:50:12 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #108,672,146 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e2e4e47…2005
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7716f31b…1366
0x34b655…2a6f
4 touches
1 conflict
0x78ffae89…d680
0x34b655…2a6f
4 touches
1 conflict
0x0e9c3b2f…d2b7
0x34b655…2a6f
2 touches
0 conflicts
0x25957369…c648
0x34b655…2a6f
2 touches
0 conflicts
0x72083f0d…082a
0x34b655…2a6f
2 touches
0 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x7e2e4e474b…0d2005
Audit this contract →
← previous block·next block →recent activity