← previous blocknext block →recent activity
Analyzing
Block #94,479,357
17 transactions · 12 stateful · 2026-08-09 11:38:46 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,479,357 · 17 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
2w03w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc66c5d79…43a8
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0xf15273a1…2c52
0x34b655…2a6f
4 touches
1 conflict
0x7e7ffece…711d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xc66c5d7903…1d43a8
Audit this contract →
← previous block·next block →recent activity