← previous blocknext block →recent activity
Analyzing
Block #93,594,953
11 transactions · 11 stateful · 2026-08-06 09:14:54 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,594,953 · 11 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
2w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8743e1ba…8331
0x34b655…2a6f
8 touches
6 conflicts
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x66503c30…8f6a
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1c2ef827…7d44
0x065c9d…c394
2 touches
0 conflicts
0x2d559fd4…9449
0x065c9d…c394
2 touches
0 conflicts
0x46333ede…fb36
0x065c9d…c394
2 touches
0 conflicts
0x6ceaec93…7838
0x065c9d…c394
2 touches
0 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 0x8743e1bab8…0a8331
Audit this contract →
← previous block·next block →recent activity