← previous blocknext block →recent activity
Analyzing
Block #94,760,470
15 transactions · 15 stateful · 2026-08-10 11:14:09 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,760,470 · 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
1w03w14w07w08w19w210w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0xecfe09ea…21d2
0x34b655…2a6f
4 touches
1 conflict
0x7d653dc5…3fe5
0x34b655…2a6f
4 touches
1 conflict
0xc02a0cd0…d469
0xe52b14…7230
3 touches
1 conflict
0xe5a040ff…6049
0xd32edf…ff58
3 touches
1 conflict
0x46cb45de…a566
0x188d58…ea8e
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
10 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity