← previous blocknext block →recent activity
Analyzing
Block #93,388,153
24 transactions · 22 stateful · 2026-08-05 15:55:18 UTC
Parallelism
71/100
Blocked
64%
Avg conflicts / tx
1.33
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,388,153 · 24 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
1w02w13w24w35w46w47w08w19w210w311w415w518w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
12 touches
15 conflicts
0xea02471d…1542
0x34b655…2a6f
10 touches
10 conflicts
0xa4e1d30f…461a
0xd32edf…ff58
9 touches
10 conflicts
0xf3d10975…0d07
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x792299c4…16b7
0x1b6862…e19c
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity