← previous blocknext block →recent activity
Analyzing
Block #96,278,194
7 transactions · 7 stateful · 2026-08-15 18:44:02 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,278,194 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49ffd065…33d1
0x34b655…2a6f
4 touches
1 conflict
0x991e2e20…94a6
0x34b655…2a6f
4 touches
1 conflict
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0x24223eb9…13ba
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d5
0x34b655…2a6f
2 touches
0 conflicts
0x2a34bb88…04d6
0x34b655…2a6f
2 touches
0 conflicts
0x35a9f06c…7689
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
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 0x49ffd065b3…cd33d1
Audit this contract →
← previous block·next block →recent activity