← previous blocknext block →recent activity
Analyzing
Block #96,350,999
13 transactions · 13 stateful · 2026-08-16 00:50:12 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,350,999 · 13 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
3w04w15w16w07w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2fd61111…5bbc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe4e9d128…437d
0x34b655…2a6f
4 touches
1 conflict
0x1310aecc…9e7b
0x34b655…2a6f
4 touches
1 conflict
0x3beed133…720d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc3fc40da…1c60
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 0x2fd61111d8…455bbc
Audit this contract →
← previous block·next block →recent activity