← previous blocknext block →recent activity
Analyzing
Block #92,012,961
19 transactions · 19 stateful · 2026-07-31 20:36:06 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,012,961 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w16w27w28w39w412w013w114w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb02a2ad…5b1a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
8 touches
6 conflicts
0xe8295039…35d3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x26444b91…765e
0x34b655…2a6f
6 touches
3 conflicts
0x65487580…b5eb
0x34b655…2a6f
6 touches
3 conflicts
0x811cb01f…e507
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
6 conflicts on slot 0xdb02a2ad0d…eb5b1a
Audit this contract →
← previous block·next block →recent activity