← previous blocknext block →recent activity
Analyzing
Block #92,338,043
10 transactions · 9 stateful · 2026-08-01 23:51:03 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,338,043 · 10 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
4w05w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdeb57ca…d796
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0006
0x7b9256…1fb2
4 touches
1 conflict
0x9df0237c…cb2f
0x7b9256…1fb2
4 touches
1 conflict
0x9df0237c…cb30
0x7b9256…1fb2
4 touches
1 conflict
0x9df0237c…cb33
0x7b9256…1fb2
4 touches
1 conflict
0xcdeb57ca…d795
0x7b9256…1fb2
4 touches
1 conflict
0x31b39922…1e65
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
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 0xcdeb57caea…84d796
Audit this contract →
← previous block·next block →recent activity