← previous blocknext block →recent activity
Analyzing
Block #92,223,104
19 transactions · 18 stateful · 2026-08-01 14:12:58 UTC
Parallelism
74/100
Blocked
56%
Avg conflicts / tx
1.05
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,223,104 · 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
1w02w13w25w06w17w29w310w011w112w213w314w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfac41145…7cfc
0x7b9256…1fb2
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x177211e2…1c2d
0x754704…b603
8 touches
6 conflicts
0xe1f61186…e2f8
0x754704…b603
8 touches
6 conflicts
0x00000000…0006
0x7b9256…1fb2
8 touches
6 conflicts
0xb1634d47…5658
0x7b9256…1fb2
8 touches
6 conflicts
0xb1634d47…5659
0x7b9256…1fb2
8 touches
6 conflicts
0xfac41145…7cf8
0x7b9256…1fb2
8 touches
6 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
6 conflicts on slot 0xfac411457b…827cfc
Audit this contract →
← previous block·next block →recent activity