← previous blocknext block →recent activity
Analyzing
Block #93,503,873
19 transactions · 18 stateful · 2026-08-06 01:37:03 UTC
Parallelism
68/100
Blocked
33%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,503,873 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w17w28w310w011w112w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41212c1d…88e3
0x34b655…2a6f
10 touches
10 conflicts
0xc6000ba5…8d65
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x28a16592…3e24
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x53edbc04…ae28
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
10 conflicts on slot 0x41212c1d51…4788e3
Audit this contract →
← previous block·next block →recent activity