← previous blocknext block →recent activity
Analyzing
Block #92,014,273
16 transactions · 14 stateful · 2026-07-31 20:42:42 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,014,273 · 16 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
1w03w06w07w08w19w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2d3fe13…b828
0x34b655…2a6f
4 touches
1 conflict
0xe603fd46…dbe6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x1e2721…7805
4 touches
1 conflict
0x0e0c66fe…796f
0x1e2721…7805
4 touches
1 conflict
0x431fa96d…6ac0
0x754704…b603
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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: Perpl
1 conflict on slot 0xd2d3fe1336…0db828
Audit this contract →
← previous block·next block →recent activity