← previous blocknext block →recent activity
Analyzing
Block #93,666,506
11 transactions · 11 stateful · 2026-08-06 15:14:37 UTC
Parallelism
45/100
Blocked
45%
Avg conflicts / tx
1.36
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,666,506 · 11 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
1w02w13w24w36w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1e56f6b6…5940
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x2281e3ba…1d5b
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xfe2577ac…677b
0x34b655…2a6f
4 touches
1 conflict
0x06f6aac6…a25d
0x34b655…2a6f
4 touches
1 conflict
0x4e50038e…6e29
0x34b655…2a6f
4 touches
1 conflict
0x5e53f676…a69c
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
10 conflicts on slot 0x1e56f6b6e1…615940
Audit this contract →
← previous block·next block →recent activity