← previous blocknext block →recent activity
Analyzing
Block #91,430,953
40 transactions · 30 stateful · 2026-07-29 19:48:15 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
2.1
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,430,953 · 40 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w112w013w114w215w316w017w118w219w320w421w522w623w724w825w928w1030w431w234w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
22 touches
55 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
10 touches
10 conflicts
0x0672e4a2…8d1f
0x34b655…2a6f
10 touches
10 conflicts
0xe377f277…1eba
0x34b655…2a6f
8 touches
6 conflicts
0xbe9baf16…df37
0x34b655…2a6f
8 touches
6 conflicts
0x966e45cf…0f25
0x34b655…2a6f
8 touches
6 conflicts
0x64e250ad…7383
0xd32edf…ff58
7 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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: Perpl
55 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity