← previous blocknext block →recent activity
Analyzing
Block #93,445,427
16 transactions · 16 stateful · 2026-08-05 20:43:14 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,445,427 · 16 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
4w05w18w29w310w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x827557c1…a6be
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x1f00a5b3…bf76
0x34b655…2a6f
4 touches
1 conflict
0x2a431ace…5f07
0x34b655…2a6f
4 touches
1 conflict
0x2f85f065…06be
0x34b655…2a6f
4 touches
1 conflict
0x3731304a…759b
0x34b655…2a6f
4 touches
1 conflict
0x4f25162a…86c5
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
6 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity