← previous blocknext block →recent activity
Analyzing
Block #95,916,269
17 transactions · 14 stateful · 2026-08-14 12:23:23 UTC
Parallelism
65/100
Blocked
50%
Avg conflicts / tx
1.06
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,916,269 · 17 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
2w05w06w17w29w310w012w113w115w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x9fbc6a76…9c29
0x34b655…2a6f
6 touches
3 conflicts
0xdec6a8f8…be18
0x34b655…2a6f
6 touches
3 conflicts
0x31519d10…f76b
0x34b655…2a6f
6 touches
3 conflicts
0x57b57f51…2449
0x34b655…2a6f
4 touches
1 conflict
0x61e7b277…fee7
0x34b655…2a6f
4 touches
1 conflict
0x63ad92a0…7912
0x34b655…2a6f
4 touches
1 conflict
0x1803586e…d149
0xa6afd3…d132
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
15 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity