← previous blocknext block →recent activity
Analyzing
Block #95,536,121
24 transactions · 24 stateful · 2026-08-13 04:30:02 UTC
Parallelism
92/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,536,121 · 24 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x286c982e…bbf4
0xa6afd3…d132
3 touches
1 conflict
0x0b0611f7…e63a
0x34b655…2a6f
2 touches
0 conflicts
0x2d1df17e…b68c
0x34b655…2a6f
2 touches
0 conflicts
0x37c2575e…b29c
0x34b655…2a6f
2 touches
0 conflicts
0x4efae872…6aa8
0x34b655…2a6f
2 touches
0 conflicts
0x5791dd54…0d85
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity