← previous blocknext block →recent activity
Analyzing
Block #94,816,421
15 transactions · 14 stateful · 2026-08-10 15:55:36 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,816,421 · 15 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
2w04w15w26w38w09w111w213w014w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7462b8f2…6312
0x34b655…2a6f
6 touches
3 conflicts
0xe44c4fc1…43b1
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
4 touches
1 conflict
0xa169711f…c7f3
0x34b655…2a6f
4 touches
1 conflict
0xa6b89ebb…a66e
0x34b655…2a6f
4 touches
1 conflict
0xc17e8f36…5f58
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 0x7462b8f2c2…8d6312
Audit this contract →
← previous block·next block →recent activity