← previous blocknext block →recent activity
Analyzing
Block #93,484,785
26 transactions · 22 stateful · 2026-08-06 00:01:05 UTC
Parallelism
77/100
Blocked
45%
Avg conflicts / tx
0.85
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,484,785 · 26 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
2w03w14w09w110w214w218w319w420w521w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0x89678d1b…463e
0xa6afd3…d132
8 touches
6 conflicts
0xa1ff0729…0146
0xa6afd3…d132
8 touches
6 conflicts
0x3b83787f…3a8a
0x34b655…2a6f
6 touches
3 conflicts
0xdb067026…9eb8
0x2b46c0…1669
4 touches
1 conflict
0x03d06590…6fac
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 0x52b477bcb8…5d7ccf
Audit this contract →
← previous block·next block →recent activity