← previous blocknext block →recent activity
Analyzing
Block #93,368,347
20 transactions · 20 stateful · 2026-08-05 14:15:42 UTC
Parallelism
65/100
Blocked
40%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,368,347 · 20 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
1w03w04w16w27w39w410w514w116w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xf5ea108a…dbf6
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x2c390858…b1ed
0x34b655…2a6f
6 touches
3 conflicts
0x41f1e2e5…2edf
0x34b655…2a6f
6 touches
3 conflicts
0xd94c5ae0…6101
0x34b655…2a6f
6 touches
3 conflicts
0x3939eef2…95ad
0x34b655…2a6f
4 touches
1 conflict
0x3b18ecc3…dc4f
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity