← previous blocknext block →recent activity
Analyzing
Block #93,329,696
14 transactions · 13 stateful · 2026-08-05 11:01:22 UTC
Parallelism
50/100
Blocked
54%
Avg conflicts / tx
0.93
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,329,696 · 14 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w38w49w511w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1a9064c9…c8ca
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf06cb710…1a9a
0x34b655…2a6f
6 touches
3 conflicts
0xcda18b0b…6a4c
0x34b655…2a6f
6 touches
3 conflicts
0x88bca116…a51e
0x34b655…2a6f
6 touches
3 conflicts
0xa1bc82c5…38df
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
6 conflicts on slot 0x1a9064c924…9cc8ca
Audit this contract →
← previous block·next block →recent activity