← previous blocknext block →recent activity
Analyzing
Block #94,852,314
30 transactions · 29 stateful · 2026-08-10 18:56:12 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1.17
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,852,314 · 30 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
1w02w14w17w08w29w310w311w012w113w114w217w224w425w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
10 touches
10 conflicts
0x11258774…9892
0x2a68ba…90c5
8 touches
6 conflicts
0xb33ff823…1188
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x160f117d…8e90
0x065c9d…c394
8 touches
6 conflicts
0x38a3f0db…80da
0xd32edf…ff58
7 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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
10 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity