← previous blocknext block →recent activity
Analyzing
Block #96,554,048
13 transactions · 12 stateful · 2026-08-16 17:51:44 UTC
Parallelism
54/100
Blocked
50%
Avg conflicts / tx
0.62
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,554,048 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w27w38w49w510w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x73320e64…b06f
0x34b655…2a6f
6 touches
3 conflicts
0xb67df4fa…af6d
0x34b655…2a6f
6 touches
3 conflicts
0x2ff3f6a5…509a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002d
0x1b6862…e19c
4 touches
1 conflict
0x6aa624fd…a850
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x177d036a…1c5d
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
3 conflicts on slot 0x73320e6460…2db06f
Audit this contract →
← previous block·next block →recent activity