← previous blocknext block →recent activity
Analyzing
Block #93,921,128
21 transactions · 18 stateful · 2026-08-07 12:35:08 UTC
Parallelism
71/100
Blocked
67%
Avg conflicts / tx
1.24
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,921,128 · 21 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
1w02w13w24w16w07w18w29w310w411w514w218w319w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
10 touches
10 conflicts
0xf275b4ca…57b8
0xe52b14…7230
10 touches
10 conflicts
0x8ffa3328…ce11
0xe52b14…7230
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe1902c61…65ad
0xe52b14…7230
6 touches
3 conflicts
0x4f1ad4b4…e00a
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
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