← previous blocknext block →recent activity
Analyzing
Block #93,498,834
20 transactions · 19 stateful · 2026-08-06 01:11:43 UTC
Parallelism
65/100
Blocked
37%
Avg conflicts / tx
1.15
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,498,834 · 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
5w06w17w28w39w010w111w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8814f69c…42b3
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xbeedaa05…9eda
0x34b655…2a6f
8 touches
6 conflicts
0x94bb14fe…8f47
0x34b655…2a6f
8 touches
6 conflicts
0xfaf89f45…ced6
0x34b655…2a6f
6 touches
3 conflicts
0x3cf50d44…961b
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
15 conflicts on slot 0x8814f69c3b…8042b3
Audit this contract →
← previous block·next block →recent activity