← previous blocknext block →recent activity
Analyzing
Block #93,671,765
26 transactions · 24 stateful · 2026-08-06 15:41:03 UTC
Parallelism
81/100
Blocked
42%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,671,765 · 26 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
1w02w03w17w010w111w212w013w014w115w216w317w418w221w125w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ffa3328…ce11
0xe52b14…7230
10 touches
10 conflicts
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0xe1902c61…65ad
0xe52b14…7230
8 touches
6 conflicts
0xd59dff32…73a2
0xe52b14…7230
6 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xa6e37efb…afc0
0xe52b14…7230
6 touches
3 conflicts
0xf275b4ca…57b8
0xe52b14…7230
6 touches
3 conflicts
0x575cf6b6…6e87
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: 0xe52b1424…bb7230
10 conflicts on slot 0x8ffa332881…c9ce11
Audit this contract →
← previous block·next block →recent activity