← previous blocknext block →recent activity
Analyzing
Block #94,287,122
8 transactions · 6 stateful · 2026-08-08 19:22:34 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,287,122 · 8 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
2w03w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x109d8a52…a7b7
0x34b655…2a6f
6 touches
3 conflicts
0xe930fa7a…2d1e
0x34b655…2a6f
6 touches
3 conflicts
0x21ef0807…d889
0x34b655…2a6f
4 touches
1 conflict
0x7b3a40f9…3e49
0x34b655…2a6f
4 touches
1 conflict
0x0d461d23…e3fb
0x34b655…2a6f
2 touches
0 conflicts
0x1bee5aea…5f61
0x34b655…2a6f
2 touches
0 conflicts
0x3e69adfb…3b62
0x34b655…2a6f
2 touches
0 conflicts
0x3fff7ccd…5a48
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
3 conflicts on slot 0x109d8a5293…02a7b7
Audit this contract →
← previous block·next block →recent activity