← previous blocknext block →recent activity
Analyzing
Block #93,921,873
19 transactions · 18 stateful · 2026-08-07 12:38:53 UTC
Parallelism
68/100
Blocked
56%
Avg conflicts / tx
1.11
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,921,873 · 19 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
1w02w13w04w06w07w18w29w310w411w512w114w115w216w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0x58733c38…f2cd
0xe52b14…7230
8 touches
6 conflicts
0x3cebc8f1…975c
0xe52b14…7230
8 touches
6 conflicts
0x693b762e…1fcd
0xe52b14…7230
8 touches
6 conflicts
0x6a3749da…c493
0xe52b14…7230
8 touches
6 conflicts
0x6ad5feb6…5606
0xe52b14…7230
8 touches
6 conflicts
0xc4a2f619…eb38
0xe52b14…7230
8 touches
6 conflicts
0xd4e69a1d…6139
0xe52b14…7230
8 touches
6 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