← previous blocknext block →recent activity
Analyzing
Block #93,360,643
24 transactions · 22 stateful · 2026-08-05 13:36:58 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,360,643 · 24 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
1w02w05w07w08w110w114w216w119w020w122w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68a2902c…b23f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x07d8b1e8…78c6
0x34b655…2a6f
4 touches
1 conflict
0x0a0cecef…4ed0
0x34b655…2a6f
4 touches
1 conflict
0x0ab6d83d…4965
0x34b655…2a6f
4 touches
1 conflict
0x1fd19887…8e0e
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 0x68a2902c52…e3b23f
Audit this contract →
← previous block·next block →recent activity