← previous blocknext block →recent activity
Analyzing
Block #94,810,445
25 transactions · 19 stateful · 2026-08-10 15:25:32 UTC
Parallelism
72/100
Blocked
37%
Avg conflicts / tx
0.52
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,810,445 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w311w413w521w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x840d3ab7…c8c4
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x025fef2f…9738
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x8905db2e…630c
0x34b655…2a6f
4 touches
1 conflict
0x00842ba8…bdc6
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 0x840d3ab7c3…edc8c4
Audit this contract →
← previous block·next block →recent activity