← previous blocknext block →recent activity
Analyzing
Block #92,358,031
21 transactions · 20 stateful · 2026-08-02 01:31:34 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,358,031 · 21 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
2w03w14w26w18w311w012w113w216w017w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x76561a25…dfeb
0x7b9256…1fb2
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xda27c764…7fab
0x34b655…2a6f
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x3006dbb7…777d
0x7b9256…1fb2
6 touches
3 conflicts
0x3006dbb7…777e
0x7b9256…1fb2
6 touches
3 conflicts
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: 0x7b9256fd…e21fb2
3 conflicts on slot 0x76561a25fd…b9dfeb
Audit this contract →
← previous block·next block →recent activity