← previous blocknext block →recent activity
Analyzing
Block #93,920,475
25 transactions · 24 stateful · 2026-08-07 12:31:51 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.64
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,920,475 · 25 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
2w03w14w25w36w47w58w69w311w518w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51232c8c…f30e
0xe52b14…7230
12 touches
15 conflicts
0xa6e37efb…afc0
0xe52b14…7230
12 touches
15 conflicts
0x87d52e62…4d17
0xe52b14…7230
12 touches
15 conflicts
0x51232c8c…f30c
0xe52b14…7230
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
12 touches
15 conflicts
0xf275b4ca…57b8
0xe52b14…7230
12 touches
15 conflicts
0x106c514d…bd94
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 0x51232c8c1f…6df30e
Audit this contract →
← previous block·next block →recent activity