← previous blocknext block →recent activity
Analyzing
Block #96,121,514
12 transactions · 9 stateful · 2026-08-15 05:35:55 UTC
Parallelism
83/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,121,514 · 12 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
4w07w18w09w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00d60c65…745d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0xe8377f79…5f5e
0x34b655…2a6f
4 touches
1 conflict
0x948e8d20…a8df
0x34b655…2a6f
4 touches
1 conflict
0x53f393fa…00b9
0x34b655…2a6f
2 touches
0 conflicts
0x76c4467d…ce28
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 0x00d60c658f…31745d
Audit this contract →
← previous block·next block →recent activity