← previous blocknext block →recent activity
Analyzing
Block #94,845,549
11 transactions · 10 stateful · 2026-08-10 18:22:09 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,845,549 · 11 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
1w05w16w27w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bd0ab04…6da7
0x34b655…2a6f
6 touches
3 conflicts
0xdeaa385f…6b8b
0x34b655…2a6f
6 touches
3 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x1c796c6b…064e
0x34b655…2a6f
4 touches
1 conflict
0x78d18f75…b521
0x34b655…2a6f
4 touches
1 conflict
0x231c5e70…ae04
0x34b655…2a6f
2 touches
0 conflicts
0x33708be5…6990
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 0x9bd0ab0401…c16da7
Audit this contract →
← previous block·next block →recent activity