← previous blocknext block →recent activity
Analyzing
Block #92,696,253
13 transactions · 13 stateful · 2026-08-03 05:53:32 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,696,253 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w18w29w310w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x8a5ced1c…3b29
0x34b655…2a6f
8 touches
6 conflicts
0x706c758c…2fdb
0x34b655…2a6f
6 touches
3 conflicts
0x87be5077…5a5b
0x34b655…2a6f
6 touches
3 conflicts
0x898d9b8a…d1ef
0x34b655…2a6f
6 touches
3 conflicts
0xc5115a1c…f19d
0x34b655…2a6f
6 touches
3 conflicts
0x7d6b9af1…9a38
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity