← previous blocknext block →recent activity
Analyzing
Block #91,070,717
39 transactions · 35 stateful · 2026-07-28 13:33:38 UTC
Parallelism
64/100
Blocked
63%
Avg conflicts / tx
1.72
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,070,717 · 39 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
2w03w16w29w010w111w012w113w214w315w416w520w721w324w226w327w431w836w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x957c875f…b3f9
0x34b655…2a6f
8 touches
6 conflicts
0x4fa49ab2…3116
0x34b655…2a6f
8 touches
6 conflicts
0x6f900be0…cd6e
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5373d1ea…127e
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: Perpl
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity