← previous blocknext block →recent activity
Analyzing
Block #91,430,781
50 transactions · 41 stateful · 2026-07-29 19:47:23 UTC
Parallelism
70/100
Blocked
61%
Avg conflicts / tx
1.7
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #91,430,781 · 50 txs across 15 waves · depth 15
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
wave w14
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w18w114w015w116w217w318w419w525w627w628w731w833w234w135w839w941w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x80ac2fd6…dcf5
0x34b655…2a6f
10 touches
10 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
10 touches
10 conflicts
0xda2ee2e7…968a
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…004c
0x80c745…7210
8 touches
6 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
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
21 conflicts on slot 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity