← previous blocknext block →recent activity
Analyzing
Block #92,061,606
12 transactions · 12 stateful · 2026-08-01 00:40:46 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #92,061,606 · 12 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
1w02w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x278b2177…46f2
0x7b9256…1fb2
4 touches
1 conflict
0x8e5da640…aea7
0x7b9256…1fb2
4 touches
1 conflict
0x8e5da640…aea8
0x7b9256…1fb2
4 touches
1 conflict
0x278b2177…46f5
0x7b9256…1fb2
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c3
0x1b6862…e19c
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 0x278b217733…ef46f2
Audit this contract →
← previous block·next block →recent activity