← previous blocknext block →recent activity
Analyzing
Block #94,969,386
12 transactions · 11 stateful · 2026-08-11 04:45:00 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,969,386 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w06w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2b5101ac…090b
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc4328d82…54c2
0x34b655…2a6f
4 touches
1 conflict
0xf4f18a3d…61d4
0x34b655…2a6f
4 touches
1 conflict
0xfb2e822f…0cd7
0x34b655…2a6f
3 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
6 conflicts on slot 0x2b5101acd1…7c090b
Audit this contract →
← previous block·next block →recent activity