← previous blocknext block →recent activity
Analyzing
Block #95,030,682
10 transactions · 9 stateful · 2026-08-11 09:53:19 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,030,682 · 10 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
2w03w04w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x87f29f74…7c8b
0x34b655…2a6f
4 touches
1 conflict
0xd58e5c6b…7188
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xaf89f1e5…4781
0xe52b14…7230
3 touches
1 conflict
0x7e92a8bd…fa3e
0x34b655…2a6f
2 touches
0 conflicts
0x8f203394…f2db
0x34b655…2a6f
2 touches
0 conflicts
0x8f203394…f2dc
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 0x87f29f742c…1d7c8b
Audit this contract →
← previous block·next block →recent activity