← previous blocknext block →recent activity
Analyzing
Block #95,193,791
13 transactions · 11 stateful · 2026-08-11 23:34:34 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,193,791 · 13 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8bd73f8…27d6
0x34b655…2a6f
4 touches
1 conflict
0xce8f28d3…f084
0x34b655…2a6f
4 touches
1 conflict
0x020c86b9…acbf
0x34b655…2a6f
4 touches
1 conflict
0x3a921be0…779c
0x2a68ba…90c5
2 touches
0 conflicts
0x01dada3b…0aa7
0x34b655…2a6f
2 touches
0 conflicts
0x01dada3b…0aa8
0x34b655…2a6f
2 touches
0 conflicts
0x0610584e…91d5
0x34b655…2a6f
2 touches
0 conflicts
0x23769ebc…c8ed
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 0xd8bd73f832…ac27d6
Audit this contract →
← previous block·next block →recent activity