← previous blocknext block →recent activity
Analyzing
Block #93,174,335
26 transactions · 25 stateful · 2026-08-04 22:00:15 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,174,335 · 26 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
1w02w13w06w07w110w011w013w114w115w216w117w319w223w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3e72a2d1…ce0e
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x15eb6170…3da3
0x34b655…2a6f
6 touches
3 conflicts
0xfe449cf3…289f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x207e9f25…4724
0x34b655…2a6f
6 touches
3 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x207e9f25…4725
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 0x3e72a2d19b…abce0e
Audit this contract →
← previous block·next block →recent activity