← previous blocknext block →recent activity
Analyzing
Block #96,302,919
15 transactions · 15 stateful · 2026-08-15 20:48:23 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,302,919 · 15 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
1w02w13w06w27w38w19w213w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4abfb389…18f4
0x34b655…2a6f
4 touches
1 conflict
0xe8366594…a96e
0x34b655…2a6f
4 touches
1 conflict
0x6d74089c…c836
0x34b655…2a6f
4 touches
1 conflict
0x79b6ccd1…6253
0x34b655…2a6f
4 touches
1 conflict
0x9e089d27…ab74
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 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity