← previous blocknext block →recent activity
Analyzing
Block #92,814,410
16 transactions · 15 stateful · 2026-08-03 15:48:11 UTC
Parallelism
56/100
Blocked
67%
Avg conflicts / tx
1.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,814,410 · 16 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
1w02w13w25w36w47w58w610w612w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dfe7788…8d9f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0x1526b11f…8b21
0x34b655…2a6f
6 touches
3 conflicts
0x9ad5901a…ce7c
0x34b655…2a6f
6 touches
3 conflicts
0x7c93b38a…9e69
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
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
21 conflicts on slot 0x7dfe77881e…028d9f
Audit this contract →
← previous block·next block →recent activity