← previous blocknext block →recent activity
Analyzing
Block #93,665,287
20 transactions · 19 stateful · 2026-08-06 15:08:29 UTC
Parallelism
75/100
Blocked
58%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,665,287 · 20 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
1w02w03w14w25w36w17w28w39w010w111w213w414w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x99c5409a…25b7
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xe9452241…95a3
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0xbf3cbeb8…99f0
0x34b655…2a6f
6 touches
3 conflicts
0x6bab0076…422b
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 0x99c5409a28…0025b7
Audit this contract →
← previous block·next block →recent activity