← previous blocknext block →recent activity
Analyzing
Block #93,750,896
30 transactions · 28 stateful · 2026-08-06 22:18:52 UTC
Parallelism
77/100
Blocked
57%
Avg conflicts / tx
1.3
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,750,896 · 30 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w08w19w210w011w112w213w314w415w516w317w126w427w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xab063d29…bb8f
0xe52b14…7230
12 touches
15 conflicts
0xf275b4ca…57b8
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
8 touches
6 conflicts
0x2fd12b6c…02cc
0x34b655…2a6f
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 0x51232c8c1f…6df30e
Audit this contract →
← previous block·next block →recent activity