← previous blocknext block →recent activity
Analyzing
Block #91,090,061
16 transactions · 16 stateful · 2026-07-28 15:11:00 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
1.44
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #91,090,061 · 16 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
1w02w13w05w16w17w28w39w410w511w6
- 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
0x2cd9f055…4912
0x34b655…2a6f
9 touches
10 conflicts
0x34806b11…bdf5
0x34b655…2a6f
6 touches
3 conflicts
0xd4bcf904…38ea
0x34b655…2a6f
5 touches
3 conflicts
0xf0d45ffd…89cf
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