← previous blocknext block →recent activity
Analyzing
Block #93,362,005
15 transactions · 15 stateful · 2026-08-05 13:43:49 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,362,005 · 15 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
3w04w15w26w38w09w111w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x733a5000…6e67
0x34b655…2a6f
6 touches
3 conflicts
0x4c214bb3…c5d3
0x34b655…2a6f
4 touches
1 conflict
0x71220f1c…2238
0x34b655…2a6f
4 touches
1 conflict
0x1a287886…0266
0xa6afd3…d132
4 touches
1 conflict
0xf1faa605…f919
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x98fc5672…13c7
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
3 conflicts on slot 0x733a5000e7…e16e67
Audit this contract →
← previous block·next block →recent activity