← previous blocknext block →recent activity
Analyzing
Block #95,200,508
14 transactions · 12 stateful · 2026-08-12 00:08:21 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,200,508 · 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
4w06w07w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a2233ee…d60f
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x0d2de0f6…e6c6
0x34b655…2a6f
4 touches
1 conflict
0x2e77c6ca…f7c6
0x34b655…2a6f
2 touches
0 conflicts
0x3ad05bcb…cdde
0x34b655…2a6f
2 touches
0 conflicts
0x4b8f0c69…87d3
0x34b655…2a6f
2 touches
0 conflicts
0x59d3778a…5033
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 0x8a2233ee38…a0d60f
Audit this contract →
← previous block·next block →recent activity