← previous blocknext block →recent activity
Analyzing
Block #96,144,180
11 transactions · 11 stateful · 2026-08-15 07:30:00 UTC
Parallelism
55/100
Blocked
36%
Avg conflicts / tx
1.09
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,144,180 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe166ac70…4fd5
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x6c28863e…840e
0x34b655…2a6f
6 touches
3 conflicts
0x2d309e75…86c0
0x34b655…2a6f
6 touches
3 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
6 touches
3 conflicts
0x5e7e0120…7bb9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
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 0xe166ac70ed…974fd5
Audit this contract →
← previous block·next block →recent activity