← previous blocknext block →recent activity
Analyzing
Block #93,671,107
29 transactions · 25 stateful · 2026-08-06 15:37:45 UTC
Parallelism
83/100
Blocked
44%
Avg conflicts / tx
0.9
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,671,107 · 29 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
1w02w13w24w05w38w09w110w211w418w321w122w423w224w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x86636855…d15b
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xbfef84b3…2ec3
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x705ab4ae…0162
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity