← previous blocknext block →recent activity
Analyzing
Block #96,024,436
13 transactions · 13 stateful · 2026-08-14 21:27:39 UTC
Parallelism
62/100
Blocked
38%
Avg conflicts / tx
1.08
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,024,436 · 13 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
2w03w04w16w07w28w19w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7c4db97…948e
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x31616f97…1acc
0x34b655…2a6f
6 touches
3 conflicts
0xbf7817bc…52f6
0x34b655…2a6f
5 touches
3 conflicts
0x4f394483…ff62
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0xb4f3dc79…9331
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
10 conflicts on slot 0xa7c4db979d…55948e
Audit this contract →
← previous block·next block →recent activity