← previous blocknext block →recent activity
Analyzing
Block #94,912,280
25 transactions · 22 stateful · 2026-08-10 23:57:46 UTC
Parallelism
68/100
Blocked
45%
Avg conflicts / tx
1.28
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,912,280 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w59w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x11b69a7e…334e
0x01bff4…1071
8 touches
6 conflicts
0x8fb50369…d3d2
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x8e1c9dd0…3bf0
0x851145…3f07
6 touches
3 conflicts
0x07b86c51…cdae
0x2a68ba…90c5
6 touches
3 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
21 conflicts on slot 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity