← previous blocknext block →recent activity
Analyzing
Block #95,297,236
11 transactions · 11 stateful · 2026-08-12 08:24:07 UTC
Parallelism
73/100
Blocked
27%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,297,236 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x699ee60f…de01
0x34b655…2a6f
6 touches
3 conflicts
0x7e3cc3e1…ced8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…000f
0x78999c…f371
4 touches
1 conflict
0xe0659a3f…90d9
0x000000…a032
4 touches
1 conflict
0x6ac4a9ce…5f63
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xcf8e8419…c691
0x34b655…2a6f
4 touches
1 conflict
0xea3b49a7…24d7
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: Perpl
3 conflicts on slot 0x699ee60f74…58de01
Audit this contract →
← previous block·next block →recent activity