← previous blocknext block →recent activity
Analyzing
Block #94,473,235
28 transactions · 27 stateful · 2026-08-09 11:07:59 UTC
Parallelism
82/100
Blocked
26%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,473,235 · 28 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w08w09w010w211w112w313w214w424w025w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5eb187dd…b1d6
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xa6389d47…9a28
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0x9ac546da…1600
0x065c9d…c394
5 touches
3 conflicts
0x4560e5a8…b741
0x34b655…2a6f
4 touches
1 conflict
0x4755fafb…859b
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
3 conflicts on slot 0x5eb187dd4c…a6b1d6
Audit this contract →
← previous block·next block →recent activity