← previous blocknext block →recent activity
Analyzing
Block #96,143,264
7 transactions · 7 stateful · 2026-08-15 07:25:23 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,143,264 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0cc22f4…af33
0x34b655…2a6f
4 touches
1 conflict
0x16f8e14a…f6e4
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x1a31be72…cd74
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x4c214bb3…c5d3
0x34b655…2a6f
2 touches
0 conflicts
0x67bfbc55…7b2f
0x34b655…2a6f
2 touches
0 conflicts
0x7ee6007b…fd68
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 0xb0cc22f4c2…33af33
Audit this contract →
← previous block·next block →recent activity