← previous blocknext block →recent activity
Analyzing
Block #93,076,342
13 transactions · 11 stateful · 2026-08-04 13:46:44 UTC
Parallelism
69/100
Blocked
55%
Avg conflicts / tx
0.69
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,076,342 · 13 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
1w03w15w26w08w39w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb291e903…4a0d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x1a287886…0266
0xa6afd3…d132
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
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 0xb291e9034a…ab4a0d
Audit this contract →
← previous block·next block →recent activity