← previous blocknext block →recent activity
Analyzing
Block #92,360,331
17 transactions · 17 stateful · 2026-08-02 01:43:08 UTC
Parallelism
88/100
Blocked
24%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,360,331 · 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
3w04w16w07w18w09w113w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3de51d22…fa54
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
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
0x1bacad10…c6f3
0x34b655…2a6f
4 touches
1 conflict
0x2f4b1dc8…e9fa
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 0x3de51d227c…b2fa54
Audit this contract →
← previous block·next block →recent activity