← previous blocknext block →recent activity
Analyzing
Block #92,868,136
23 transactions · 21 stateful · 2026-08-03 20:18:38 UTC
Parallelism
78/100
Blocked
33%
Avg conflicts / tx
0.39
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,868,136 · 23 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
2w03w14w05w16w211w312w418w320w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x32626666…080c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x3accf018…2e8b
0x34b655…2a6f
4 touches
1 conflict
0x7d16a9bc…25db
0x34b655…2a6f
4 touches
1 conflict
0xcef70a96…db44
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
3 conflicts on slot 0x3262666637…ed080c
Audit this contract →
← previous block·next block →recent activity