← previous blocknext block →recent activity
Analyzing
Block #93,238,648
25 transactions · 23 stateful · 2026-08-05 03:23:35 UTC
Parallelism
60/100
Blocked
48%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #93,238,648 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w27w38w413w514w615w717w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x216ffe66…1f94
0x34b655…2a6f
8 touches
6 conflicts
0x4c676afe…440e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x706c758c…2fdb
0x34b655…2a6f
6 touches
3 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
6 touches
3 conflicts
0x423d9a98…bc7c
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity