← previous blocknext block →recent activity
Analyzing
Block #93,933,675
21 transactions · 18 stateful · 2026-08-07 13:38:13 UTC
Parallelism
76/100
Blocked
56%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,933,675 · 21 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
1w02w14w05w18w19w210w311w012w113w215w117w420w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00c47ec5…dfee
0x34b655…2a6f
10 touches
10 conflicts
0xba1edffb…323e
0x34b655…2a6f
8 touches
6 conflicts
0x69411fb3…e36d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0xb6ed511f…6b68
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x00c47ec566…5cdfee
Audit this contract →
← previous block·next block →recent activity