← previous blocknext block →recent activity
Analyzing
Block #92,443,347
7 transactions · 7 stateful · 2026-08-02 08:40:36 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,443,347 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa69a8250…d650
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xce2f0b6e…0e05
0x34b655…2a6f
4 touches
1 conflict
0x00ad1f54…4c6a
0x34b655…2a6f
2 touches
0 conflicts
0x0a3b1855…e661
0x34b655…2a6f
2 touches
0 conflicts
0x24beab0f…ee70
0x34b655…2a6f
2 touches
0 conflicts
0x2b257415…b10f
0x34b655…2a6f
2 touches
0 conflicts
0x2c08e414…e319
0x34b655…2a6f
2 touches
0 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: Perpl
1 conflict on slot 0xa69a82501a…94d650
Audit this contract →
← previous block·next block →recent activity