← previous blocknext block →recent activity
Analyzing
Block #93,404,963
10 transactions · 9 stateful · 2026-08-05 17:19:48 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,404,963 · 10 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
4w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7f63a266…68c0
0x34b655…2a6f
4 touches
1 conflict
0x046e4d12…847a
0x34b655…2a6f
2 touches
0 conflicts
0x08330b36…ae29
0x34b655…2a6f
2 touches
0 conflicts
0x0ea75628…bd71
0x34b655…2a6f
2 touches
0 conflicts
0x12f97307…97c3
0x34b655…2a6f
2 touches
0 conflicts
0x135b5ad3…2161
0x34b655…2a6f
2 touches
0 conflicts
0x21605a79…d719
0x34b655…2a6f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity