← previous blocknext block →recent activity
Analyzing
Block #93,239,666
10 transactions · 9 stateful · 2026-08-05 03:28:42 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
1.3
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,239,666 · 10 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
1w02w14w05w16w27w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xa56e54d0…2d39
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x4e8df67d…c10f
0x34b655…2a6f
4 touches
1 conflict
0x7580c7a6…b73d
0x34b655…2a6f
4 touches
1 conflict
0xa644ee1f…a150
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
10 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity