← previous blocknext block →recent activity
Analyzing
Block #92,852,369
17 transactions · 16 stateful · 2026-08-03 18:59:16 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,852,369 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w36w47w58w010w512w013w114w215w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda27c764…7fab
0x34b655…2a6f
8 touches
6 conflicts
0x7fb3faa1…2dbd
0x34b655…2a6f
6 touches
3 conflicts
0xf8c9546a…ebba
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xc13fac9b…d2d1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x00000000…00c9
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 0xda27c76455…2e7fab
Audit this contract →
← previous block·next block →recent activity