← previous blocknext block →recent activity
Analyzing
Block #94,913,079
24 transactions · 20 stateful · 2026-08-11 00:01:47 UTC
Parallelism
67/100
Blocked
45%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,913,079 · 24 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w410w511w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0057fa4…2c61
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xb39cb1d8…effa
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x1d9867ad…6d9a
0x34b655…2a6f
4 touches
1 conflict
0x2bfc672f…4d29
0x34b655…2a6f
4 touches
1 conflict
0xd597209e…9800
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
21 conflicts on slot 0xc0057fa46e…362c61
Audit this contract →
← previous block·next block →recent activity