← previous blocknext block →recent activity
Analyzing
Block #93,241,137
14 transactions · 14 stateful · 2026-08-05 03:36:06 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.93
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,241,137 · 14 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
1w02w13w24w35w16w07w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x97464468…7f58
0xd32edf…ff58
7 touches
6 conflicts
0xac33ff75…077b
0xfa32f9…f3f0
4 touches
1 conflict
0xdf6c3e51…c493
0x34b655…2a6f
4 touches
1 conflict
0x99f666e3…b2a2
0x3bd359…433a
4 touches
1 conflict
0x9194f4a3…10b8
0x754704…b603
4 touches
1 conflict
0x00000000…0000
0xfa32f9…f3f0
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 0xbcbf5d09a8…c68bac
Audit this contract →
← previous block·next block →recent activity