← previous blocknext block →recent activity
Analyzing
Block #93,456,795
11 transactions · 11 stateful · 2026-08-05 21:40:23 UTC
Parallelism
55/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,456,795 · 11 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
1w02w13w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x716e338f…5e33
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x9ba6ae4a…90cb
0x34b655…2a6f
8 touches
6 conflicts
0xabd0bcfc…64e2
0x34b655…2a6f
6 touches
3 conflicts
0x3a5cd535…3546
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 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
10 conflicts on slot 0x716e338f35…3a5e33
Audit this contract →
← previous block·next block →recent activity