← previous blocknext block →recent activity
Analyzing
Block #95,032,770
13 transactions · 11 stateful · 2026-08-11 10:03:51 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,032,770 · 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
1w02w15w06w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x89b9e5f7…647c
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x3d158563…8713
0x34b655…2a6f
4 touches
1 conflict
0x26744466…9f4c
0x34b655…2a6f
2 touches
0 conflicts
0x2d58a69f…6820
0x34b655…2a6f
2 touches
0 conflicts
0x34ac5036…bedf
0x34b655…2a6f
2 touches
0 conflicts
0x4699a63a…eddc
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 0x89b9e5f72a…b4647c
Audit this contract →
← previous block·next block →recent activity