← previous blocknext block →recent activity
Analyzing
Block #95,585,179
14 transactions · 13 stateful · 2026-08-13 08:36:45 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,585,179 · 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
1w02w13w04w17w08w19w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd6b4eda…9282
0x968279…9342
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4ee5b056…c09c
0x968279…9342
4 touches
1 conflict
0xfd6b4eda…927f
0x968279…9342
4 touches
1 conflict
0xfd6b4eda…9280
0x968279…9342
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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: 0x96827978…f09342
1 conflict on slot 0xfd6b4eda54…e79282
Audit this contract →
← previous block·next block →recent activity