← previous blocknext block →recent activity
Analyzing
Block #93,923,233
16 transactions · 15 stateful · 2026-08-07 12:45:43 UTC
Parallelism
63/100
Blocked
53%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,923,233 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w37w48w59w010w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0xd7908b5f…56b9
0x34b655…2a6f
4 touches
1 conflict
0xc137f51f…cd2e
0x851145…3f07
4 touches
1 conflict
0x3caddb80…c68e
0xe52b14…7230
4 touches
1 conflict
0x3caddb80…c690
0xe52b14…7230
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: 0xe52b1424…bb7230
15 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity