← previous blocknext block →recent activity
Analyzing
Block #93,349,836
12 transactions · 11 stateful · 2026-08-05 12:42:37 UTC
Parallelism
58/100
Blocked
36%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,349,836 · 12 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
1w02w13w24w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c390858…b1ed
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xcc1d8834…64e5
0x34b655…2a6f
8 touches
6 conflicts
0x2bd4c467…ae85
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x9375a764…dca1
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 0x2c3908588c…50b1ed
Audit this contract →
← previous block·next block →recent activity