← previous blocknext block →recent activity
Analyzing
Block #94,791,630
47 transactions · 39 stateful · 2026-08-10 13:50:53 UTC
Parallelism
60/100
Blocked
72%
Avg conflicts / tx
2.98
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #94,791,630 · 47 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w18w29w310w311w412w413w514w515w616w617w718w819w920w1042w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
18 touches
36 conflicts
0x0a57a2b8…3cdd
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
16 touches
28 conflicts
0xec7d120d…7084
0x34b655…2a6f
14 touches
21 conflicts
0xa279b18d…63bc
0x34b655…2a6f
10 touches
10 conflicts
0x2840c278…bbc7
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
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
36 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity