← previous blocknext block →recent activity
Analyzing
Block #95,270,259
14 transactions · 13 stateful · 2026-08-12 06:07:57 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,270,259 · 14 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
1w02w13w04w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
4 touches
1 conflict
0x5311f864…0984
0x754704…b603
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
2 touches
0 conflicts
0x0b00aeff…7bd3
0x34b655…2a6f
2 touches
0 conflicts
0x16508ec1…b5fa
0x34b655…2a6f
2 touches
0 conflicts
0x19d0eecc…6863
0x34b655…2a6f
2 touches
0 conflicts
0x25191452…d2ed
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