← previous blocknext block →recent activity
Analyzing
Block #91,410,020
57 transactions · 45 stateful · 2026-07-29 18:02:00 UTC
Parallelism
77/100
Blocked
62%
Avg conflicts / tx
1.67
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,410,020 · 57 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w16w212w013w114w215w316w423w024w125w226w327w428w529w630w731w840w542w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
10 touches
10 conflicts
0x5a409e7f…09b6
0x2b46c0…1669
8 touches
6 conflicts
0x7a12283f…b18a
0x2b46c0…1669
8 touches
6 conflicts
0x915c095e…c1e5
0x2b46c0…1669
8 touches
6 conflicts
0xcfe06a18…b5b5
0x2b46c0…1669
8 touches
6 conflicts
0xd8fd2add…50fc
0x2b46c0…1669
8 touches
6 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
36 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity