← previous blocknext block →recent activity
Analyzing
Block #92,080,730
15 transactions · 15 stateful · 2026-08-01 02:16:57 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.73
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,080,730 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w18w29w010w111w213w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x961026a6…7aed
0x7b9256…1fb2
6 touches
3 conflicts
0x961026a6…7af1
0x7b9256…1fb2
6 touches
3 conflicts
0xfb8a9134…1d4e
0x7b9256…1fb2
6 touches
3 conflicts
0xfb8a9134…1d4f
0x7b9256…1fb2
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x961026a6…7aee
0x7b9256…1fb2
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x961026a620…887aed
Audit this contract →
← previous block·next block →recent activity