← previous blocknext block →recent activity
Analyzing
Block #92,542,672
17 transactions · 16 stateful · 2026-08-02 17:00:10 UTC
Parallelism
53/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,542,672 · 17 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
1w02w13w04w15w26w38w49w510w611w715w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5b1895ec…423a
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x42b10c57…3ee7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0xa0d3a786…91d9
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 0x5b1895ec3d…31423a
Audit this contract →
← previous block·next block →recent activity