← previous blocknext block →recent activity
Analyzing
Block #93,240,315
20 transactions · 17 stateful · 2026-08-05 03:31:58 UTC
Parallelism
80/100
Blocked
41%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,240,315 · 20 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
1w02w13w04w19w010w112w214w115w319w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2385516f…eca5
0x34b655…2a6f
4 touches
1 conflict
0x6419eb11…3680
0x34b655…2a6f
4 touches
1 conflict
0x7b7d9b6f…21e3
0x34b655…2a6f
4 touches
1 conflict
0x94de4d05…ad01
0x34b655…2a6f
4 touches
1 conflict
0xa56e54d0…2d39
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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
1 conflict on slot 0x2385516f6a…9aeca5
Audit this contract →
← previous block·next block →recent activity