← previous blocknext block →recent activity
Analyzing
Block #95,581,749
16 transactions · 15 stateful · 2026-08-13 08:19:30 UTC
Parallelism
69/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,581,749 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w17w29w210w311w112w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca30efc5…10b3
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 conflicts
0x6771eae2…7014
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7ee6007b…fd68
0x34b655…2a6f
4 touches
1 conflict
0x7f5b2c1d…0e7f
0x34b655…2a6f
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
6 conflicts on slot 0xca30efc5cc…8e10b3
Audit this contract →
← previous block·next block →recent activity