← previous blocknext block →recent activity
Analyzing
Block #95,075,816
25 transactions · 25 stateful · 2026-08-11 13:41:09 UTC
Parallelism
84/100
Blocked
56%
Avg conflicts / tx
1.12
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,075,816 · 25 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
1w02w13w14w25w06w07w18w39w010w113w214w315w217w318w319w323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x537258fd…eded
0x34b655…2a6f
8 touches
6 conflicts
0x15ead0ed…0479
0xd32edf…ff58
7 touches
6 conflicts
0xc53799eb…d928
0x34b655…2a6f
6 touches
3 conflicts
0xe283e878…7262
0x34b655…2a6f
6 touches
3 conflicts
0xef1cbbb7…8cc8
0x34b655…2a6f
6 touches
3 conflicts
0x2b5101ac…090b
0x34b655…2a6f
6 touches
3 conflicts
0x529e53cf…38e4
0xa6afd3…d132
6 touches
3 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
6 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity