← previous blocknext block →recent activity
Analyzing
Block #94,666,572
16 transactions · 14 stateful · 2026-08-10 03:20:23 UTC
Parallelism
69/100
Blocked
57%
Avg conflicts / tx
1.06
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #94,666,572 · 16 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
1w02w13w05w06w17w28w310w411w113w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xeae24c…0be0
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x76a66a12…3513
0x34b655…2a6f
6 touches
3 conflicts
0xf3383813…4a0c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x5d1ac445…5233
0x34b655…2a6f
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x79675040…2c27
0xd32edf…ff58
3 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: 0xeae24c72…e30be0
10 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity