← previous blocknext block →recent activity
Analyzing
Block #93,665,700
17 transactions · 17 stateful · 2026-08-06 15:10:34 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,665,700 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w05w26w37w48w09w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x80656e3b…9240
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xe1d743ba…11c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xd1b40f29…9b9d
0x34b655…2a6f
6 touches
3 conflicts
0xa8a56a8f…3924
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 0x80656e3b9f…e39240
Audit this contract →
← previous block·next block →recent activity