← previous blocknext block →recent activity
Analyzing
Block #95,637,161
8 transactions · 8 stateful · 2026-08-13 12:58:14 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,637,161 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32b804b3…ce18
0x34b655…2a6f
4 touches
1 conflict
0xb6ba6de1…ffd7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0xdaf4f143…58d4
0x2a68ba…90c5
2 touches
0 conflicts
0x1780c094…11da
0x34b655…2a6f
2 touches
0 conflicts
0x948836ff…59ab
0x34b655…2a6f
2 touches
0 conflicts
0xd08098a8…f0a6
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 0x32b804b3f4…fece18
Audit this contract →
← previous block·next block →recent activity