← previous blocknext block →recent activity
Analyzing
Block #95,757,386
17 transactions · 16 stateful · 2026-08-13 23:03:58 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
1.29
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #95,757,386 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w38w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x01bae8a2…d116
0x34b655…2a6f
8 touches
6 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
8 touches
6 conflicts
0xa571f0e2…e8c7
0x34b655…2a6f
8 touches
6 conflicts
0xc0b738d8…20e1
0x34b655…2a6f
8 touches
6 conflicts
0x5621c219…bbeb
0x34b655…2a6f
6 touches
3 conflicts
0x3a7fb5b5…f0e5
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x038b9243…553d
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x01bae8a23a…45d116
Audit this contract →
← previous block·next block →recent activity