← previous blocknext block →recent activity
Analyzing
Block #93,181,614
26 transactions · 21 stateful · 2026-08-04 22:36:51 UTC
Parallelism
85/100
Blocked
52%
Avg conflicts / tx
0.81
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,181,614 · 26 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
5w06w07w19w110w211w013w214w315w118w119w220w321w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
8 touches
6 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x072c6bc9…ddf1
0xd32edf…ff58
5 touches
3 conflicts
0xbd0df907…e1ef
0x065c9d…c394
5 touches
3 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
6 conflicts on slot 0x033cf007c8…d2136d
Audit this contract →
← previous block·next block →recent activity