← previous blocknext block →recent activity
Analyzing
Block #92,285,234
20 transactions · 19 stateful · 2026-08-01 19:25:28 UTC
Parallelism
90/100
Blocked
21%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,285,234 · 20 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
3w04w19w010w011w112w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe969a0fb…1f6b
0x7b9256…1fb2
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x177211e2…1c2d
0x754704…b603
4 touches
1 conflict
0xe1f61186…e2f8
0x754704…b603
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0xd452c391…556f
0x7b9256…1fb2
4 touches
1 conflict
0xd452c391…5570
0x7b9256…1fb2
4 touches
1 conflict
0xd452c391…5573
0x7b9256…1fb2
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 0xe969a0fb5e…fe1f6b
Audit this contract →
← previous block·next block →recent activity