← previous blocknext block →recent activity
Analyzing
Block #93,932,702
23 transactions · 23 stateful · 2026-08-07 13:33:20 UTC
Parallelism
78/100
Blocked
43%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,932,702 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w26w110w011w112w213w314w416w017w118w121w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
10 touches
10 conflicts
0x0b0c2e8d…c1b8
0xe52b14…7230
10 touches
10 conflicts
0x3845e7dc…c691
0xe52b14…7230
8 touches
6 conflicts
0x93e244d8…fc13
0xe52b14…7230
8 touches
6 conflicts
0x58a9a529…3ca1
0xe52b14…7230
6 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x69022a6c…ace8
0xe52b14…7230
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
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
10 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity