← previous blocknext block →recent activity
Analyzing
Block #92,560,805
8 transactions · 8 stateful · 2026-08-02 18:31:22 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,560,805 · 8 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
1w02w13w04w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc34c34a6…b46f
0x34b655…2a6f
8 touches
6 conflicts
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x5e71af98…bfd6
0x34b655…2a6f
4 touches
1 conflict
0x19b4e3fd…3821
0x34b655…2a6f
4 touches
1 conflict
0xee335a46…6d19
0x34b655…2a6f
4 touches
1 conflict
0x8e8d48a4…7a75
0x34b655…2a6f
4 touches
1 conflict
0xb2fa1675…4e07
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 0xc34c34a6fb…4db46f
Audit this contract →
← previous block·next block →recent activity