← previous blocknext block →recent activity
Analyzing
Block #93,064,201
18 transactions · 17 stateful · 2026-08-04 12:45:11 UTC
Parallelism
78/100
Blocked
59%
Avg conflicts / tx
1.06
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,064,201 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w17w09w010w112w213w314w115w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xce06a0f7…efef
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x10e77cb1…d08b
0x34b655…2a6f
5 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
4 touches
1 conflict
0xae28870c…072f
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
6 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity