← previous blocknext block →recent activity
Analyzing
Block #94,790,862
15 transactions · 14 stateful · 2026-08-10 13:47:01 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,790,862 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w08w19w010w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfca3cd0…5023
0x34b655…2a6f
6 touches
3 conflicts
0xdf3da4b2…7cd4
0x34b655…2a6f
6 touches
3 conflicts
0x99b8bc56…7466
0x34b655…2a6f
6 touches
3 conflicts
0xd2862d04…388c
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x6847107a…f468
0xa6afd3…d132
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0xbfca3cd067…cd5023
Audit this contract →
← previous block·next block →recent activity