← previous blocknext block →recent activity
Analyzing
Block #93,242,294
17 transactions · 16 stateful · 2026-08-05 03:41:55 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.41
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,242,294 · 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
1w02w13w24w35w46w57w310w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xf81be11b…2bc7
0x968279…9342
8 touches
6 conflicts
0x863c46a9…5c4e
0x968279…9342
8 touches
6 conflicts
0x863c46a9…5c51
0x968279…9342
8 touches
6 conflicts
0x863c46a9…5c52
0x968279…9342
8 touches
6 conflicts
0x863c46a9…5c53
0x968279…9342
8 touches
6 conflicts
0xf81be11b…2bc4
0x968279…9342
8 touches
6 conflicts
0xf81be11b…2bc5
0x968279…9342
8 touches
6 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
15 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity