← previous blocknext block →recent activity
Analyzing
Block #91,100,870
16 transactions · 15 stateful · 2026-07-28 16:05:25 UTC
Parallelism
50/100
Blocked
60%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #91,100,870 · 16 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w06w17w28w39w410w511w612w714w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0xbde524f4…43bf
0x34b655…2a6f
12 touches
15 conflicts
0xce06a0f7…efef
0x34b655…2a6f
12 touches
15 conflicts
0x6389e166…e1ba
0x34b655…2a6f
8 touches
6 conflicts
0x2ea57368…3ae6
0x34b655…2a6f
7 touches
6 conflicts
0x5256b248…5624
0x34b655…2a6f
5 touches
3 conflicts
0xff3d6184…43dd
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: Perpl
21 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity