← previous blocknext block →recent activity
Analyzing
Block #93,663,737
24 transactions · 23 stateful · 2026-08-06 15:00:42 UTC
Parallelism
63/100
Blocked
48%
Avg conflicts / tx
1.71
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #93,663,737 · 24 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w06w17w28w39w412w519w620w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x310afe2c…83e1
0x34b655…2a6f
14 touches
21 conflicts
0x002be092…c311
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x98212952…9ba6
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0xcc351d6d…256b
0x34b655…2a6f
8 touches
6 conflicts
0x76d1e78d…7877
0x40c49f…2af0
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
21 conflicts on slot 0x310afe2cd5…d683e1
Audit this contract →
← previous block·next block →recent activity