← previous blocknext block →recent activity
Analyzing
Block #93,177,495
14 transactions · 13 stateful · 2026-08-04 22:16:09 UTC
Parallelism
79/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,177,495 · 14 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
1w02w04w16w27w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e0
0x34b655…2a6f
4 touches
1 conflict
0x0be747d5…22e1
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
4 touches
1 conflict
0x19f3e8e5…049e
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x3c7d1716…096b
0x34b655…2a6f
4 touches
1 conflict
0x3d2e7bcf…54f9
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
1 conflict on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity