← previous blocknext block →recent activity
Analyzing
Block #92,808,244
16 transactions · 15 stateful · 2026-08-03 15:17:11 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #92,808,244 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w29w110w013w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x365ca418…bea4
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
4 touches
1 conflict
0x91d1a0a3…8cba
0x34b655…2a6f
4 touches
1 conflict
0x1c645adf…cd53
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x365ca418d0…dfbea4
Audit this contract →
← previous block·next block →recent activity