← previous blocknext block →recent activity
Analyzing
Block #92,360,324
17 transactions · 16 stateful · 2026-08-02 01:43:06 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,360,324 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w18w09w110w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x39bcabbf…b8aa
0x7b9256…1fb2
4 touches
1 conflict
0x39bcabbf…b8ab
0x7b9256…1fb2
4 touches
1 conflict
0x39bcabbf…b8ae
0x7b9256…1fb2
4 touches
1 conflict
0x3de51d22…fa53
0x7b9256…1fb2
4 touches
1 conflict
0x3de51d22…fa54
0x7b9256…1fb2
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xb5924647…4cf1
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: 0x7b9256fd…e21fb2
1 conflict on slot 0x39bcabbff6…0cb8aa
Audit this contract →
← previous block·next block →recent activity