← previous blocknext block →recent activity
Analyzing
Block #93,920,512
25 transactions · 23 stateful · 2026-08-07 12:32:03 UTC
Parallelism
76/100
Blocked
48%
Avg conflicts / tx
1.28
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,920,512 · 25 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
2w05w06w18w29w310w011w112w213w314w415w516w422w124w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf275b4ca…57b8
0xe52b14…7230
12 touches
15 conflicts
0x87d52e62…4d17
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 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 0xf275b4ca84…5d57b8
Audit this contract →
← previous block·next block →recent activity