← previous blocknext block →recent activity
Analyzing
Block #96,083,157
16 transactions · 15 stateful · 2026-08-15 02:23:01 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,083,157 · 16 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
1w02w03w14w05w08w19w210w011w312w113w115w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x44331cd1…15b0
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd63ab65f…d79e
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0x890f7ea3…b6fe
0x34b655…2a6f
4 touches
1 conflict
0x8aef18db…9238
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
6 conflicts on slot 0x44331cd11a…f015b0
Audit this contract →
← previous block·next block →recent activity