← previous blocknext block →recent activity
Analyzing
Block #92,564,020
15 transactions · 14 stateful · 2026-08-02 18:47:32 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,564,020 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w08w110w211w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d32af9…cb05
0x34b655…2a6f
6 touches
3 conflicts
0x5a0a2b03…ac50
0x34b655…2a6f
6 touches
3 conflicts
0x2c8f52ce…fe9a
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x3e3b859f…3654
0x34b655…2a6f
4 touches
1 conflict
0x2b54cadb…4425
0xd18b7e…414b
4 touches
1 conflict
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
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 0xb9d32af979…e7cb05
Audit this contract →
← previous block·next block →recent activity