← previous blocknext block →recent activity
Analyzing
Block #93,368,575
19 transactions · 19 stateful · 2026-08-05 14:16:51 UTC
Parallelism
68/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,368,575 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w27w38w49w011w112w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac8a5059…fd42
0x34b655…2a6f
8 touches
6 conflicts
0x808129fc…f97d
0x34b655…2a6f
6 touches
3 conflicts
0xa279b18d…63bc
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xf6deafb5…5c25
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x3464bbc5…a323
0xa6afd3…d132
6 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 0xac8a5059ab…e9fd42
Audit this contract →
← previous block·next block →recent activity