← previous blocknext block →recent activity
Analyzing
Block #93,363,206
17 transactions · 14 stateful · 2026-08-05 13:49:51 UTC
Parallelism
59/100
Blocked
57%
Avg conflicts / tx
1.18
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,363,206 · 17 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
2w03w16w27w38w410w011w512w114w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca94d4e6…4e69
0x34b655…2a6f
12 touches
15 conflicts
0xadc56a25…02de
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xd8bc53a3…c2fe
0x34b655…2a6f
10 touches
10 conflicts
0xe6e6f436…ddc0
0x34b655…2a6f
10 touches
10 conflicts
0x43e3decb…be40
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
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 0xca94d4e6b0…874e69
Audit this contract →
← previous block·next block →recent activity