← previous blocknext block →recent activity
Analyzing
Block #93,455,529
13 transactions · 11 stateful · 2026-08-05 21:34:01 UTC
Parallelism
69/100
Blocked
27%
Avg conflicts / tx
0.46
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,455,529 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba6ae4a…90cb
0x34b655…2a6f
8 touches
6 conflicts
0x6af3bfab…17a8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xd106eb58…b2b2
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7560
0x34b655…2a6f
4 touches
1 conflict
0xf273c816…7561
0x34b655…2a6f
4 touches
1 conflict
0xc6cece75…ea3a
0x34b655…2a6f
4 touches
1 conflict
0x4cf7fb83…65f1
0x34b655…2a6f
3 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
6 conflicts on slot 0x9ba6ae4a28…c990cb
Audit this contract →
← previous block·next block →recent activity