← previous blocknext block →recent activity
Analyzing
Block #92,078,362
18 transactions · 16 stateful · 2026-08-01 02:05:02 UTC
Parallelism
50/100
Blocked
56%
Avg conflicts / tx
2.06
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #92,078,362 · 18 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w38w49w510w611w712w813w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc1b52e91…bb8f
0x7b9256…1fb2
18 touches
36 conflicts
0x177211e2…1c2d
0x754704…b603
18 touches
36 conflicts
0xe1f61186…e2f8
0x754704…b603
18 touches
36 conflicts
0x00000000…0006
0x7b9256…1fb2
18 touches
36 conflicts
0x770b2225…e6ac
0x7b9256…1fb2
18 touches
36 conflicts
0x770b2225…e6ad
0x7b9256…1fb2
18 touches
36 conflicts
0xc1b52e91…bb8b
0x7b9256…1fb2
18 touches
36 conflicts
0xc1b52e91…bb8c
0x7b9256…1fb2
18 touches
36 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: 0x7b9256fd…e21fb2
36 conflicts on slot 0xc1b52e91ff…d6bb8f
Audit this contract →
← previous block·next block →recent activity