← previous blocknext block →recent activity
Analyzing
Block #92,543,042
15 transactions · 14 stateful · 2026-08-02 17:02:02 UTC
Parallelism
47/100
Blocked
50%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,543,042 · 15 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w59w610w011w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3adf6cd7…6f2c
0x34b655…2a6f
10 touches
10 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x9660222c…9e59
0xd32edf…ff58
7 touches
6 conflicts
0xa214976d…5939
0x34b655…2a6f
7 touches
6 conflicts
0x4abaedb1…65b9
0x34b655…2a6f
6 touches
3 conflicts
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
10 conflicts on slot 0x3adf6cd78c…676f2c
Audit this contract →
← previous block·next block →recent activity