← previous blocknext block →recent activity
Analyzing
Block #94,753,864
13 transactions · 13 stateful · 2026-08-10 10:40:50 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,753,864 · 13 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
1w02w15w06w17w28w310w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52aa1020…c85c
0x34b655…2a6f
6 touches
3 conflicts
0x8c7eac39…f34d
0x34b655…2a6f
6 touches
3 conflicts
0xf8982aa7…cbbf
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x481b500f…7ef3
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2db
0x34b655…2a6f
4 touches
1 conflict
0x8f203394…f2dc
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 0x52aa1020ce…5bc85c
Audit this contract →
← previous block·next block →recent activity