← previous blocknext block →recent activity
Analyzing
Block #94,840,402
17 transactions · 16 stateful · 2026-08-10 17:56:15 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
0.65
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,840,402 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w28w09w110w311w414w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65487580…b5eb
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xbec23443…9293
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x8299fe6c…5752
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0xcda8993c…daf7
0x34b655…2a6f
6 touches
3 conflicts
0x68256d5a…db24
0x34b655…2a6f
5 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
3 conflicts on slot 0x654875805c…59b5eb
Audit this contract →
← previous block·next block →recent activity