← previous blocknext block →recent activity
Analyzing
Block #92,244,625
35 transactions · 22 stateful · 2026-08-01 16:01:12 UTC
Parallelism
86/100
Blocked
45%
Avg conflicts / tx
0.34
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #92,244,625 · 35 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w16w27w318w319w420w021w124w026w127w230w031w132w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x971fbb87…4494
0xd32edf…ff58
5 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x6237f1a7…2f59
0x3bd359…433a
4 touches
1 conflict
0x8389816e…c06f
0x3bd359…433a
4 touches
1 conflict
0xf6cc7de8…0b4a
0x3bd359…433a
4 touches
1 conflict
0x00000000…0000
0x47bae1…7568
4 touches
1 conflict
0x00000000…0002
0x47bae1…7568
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: 0x91855e79…58ac7e
3 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity