← previous blocknext block →recent activity
Analyzing
Block #94,318,674
24 transactions · 18 stateful · 2026-08-08 22:02:33 UTC
Parallelism
88/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,318,674 · 24 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w28w09w111w012w115w017w120w221w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbadf6b0…43b2
0x33176b…e078
6 touches
3 conflicts
0x09106a95…1467
0x33176b…e078
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x5261f6ab…9aa1
0xee8c0e…1242
4 touches
1 conflict
0x2a9e9bd1…5368
0x2a68ba…90c5
4 touches
1 conflict
0x3040553c…5e28
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xe8f00c69…93b6
0xa6afd3…d132
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: 0x33176be2…ede078
3 conflicts on slot 0xdbadf6b093…d843b2
Audit this contract →
← previous block·next block →recent activity