← previous blocknext block →recent activity
Analyzing
Block #92,547,049
19 transactions · 19 stateful · 2026-08-02 17:22:11 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1.32
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #92,547,049 · 19 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
1w02w13w04w15w26w37w49w510w614w215w316w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x534ef679…ae9d
0x34b655…2a6f
8 touches
6 conflicts
0x2979e2dd…335e
0x34b655…2a6f
6 touches
3 conflicts
0x0b6aaded…1f67
0x34b655…2a6f
4 touches
1 conflict
0x2cb72281…e596
0x34b655…2a6f
4 touches
1 conflict
0x422e2fb3…1065
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity