← previous blocknext block →recent activity
Analyzing
Block #96,132,390
12 transactions · 11 stateful · 2026-08-15 06:30:41 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,132,390 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w07w19w010w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3d3cd…7281
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x2981b6be…7be0
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity