← previous blocknext block →recent activity
Analyzing
Block #94,815,358
15 transactions · 13 stateful · 2026-08-10 15:50:15 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,815,358 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w08w19w210w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x726752fc…813d
0x34b655…2a6f
8 touches
6 conflicts
0x3d158563…8713
0x34b655…2a6f
6 touches
3 conflicts
0xa8fc95a0…d6b9
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x66e13f5a…f010
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x7462b8f2…6312
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
6 conflicts on slot 0x726752fc44…16813d
Audit this contract →
← previous block·next block →recent activity