← previous blocknext block →recent activity
Analyzing
Block #94,306,007
18 transactions · 17 stateful · 2026-08-08 20:58:13 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,306,007 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w38w09w110w411w512w615w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0a57a2b8…3cdd
0x34b655…2a6f
12 touches
15 conflicts
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0x1279ed80…4a27
0x34b655…2a6f
4 touches
1 conflict
0x320178e8…b5f6
0x34b655…2a6f
4 touches
1 conflict
0x3ab86b5a…8290
0x34b655…2a6f
4 touches
1 conflict
0x736bfd85…2594
0x34b655…2a6f
4 touches
1 conflict
0x2a9e9bd1…5368
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
15 conflicts on slot 0x0a57a2b8cd…773cdd
Audit this contract →
← previous block·next block →recent activity