← previous blocknext block →recent activity
Analyzing
Block #91,396,543
46 transactions · 40 stateful · 2026-07-29 16:53:53 UTC
Parallelism
70/100
Blocked
70%
Avg conflicts / tx
2
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #91,396,543 · 46 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
4w05w16w27w310w011w112w213w314w415w016w017w118w225w726w427w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…0002
0x48cba2…b48b
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x989252a1…d812
0xa6afd3…d132
8 touches
6 conflicts
0x5a08ca7f…6546
0x34b655…2a6f
8 touches
6 conflicts
0xa779293b…5e59
0x34b655…2a6f
8 touches
6 conflicts
0xbc66586e…20fe
0x34b655…2a6f
8 touches
6 conflicts
0xda27c764…7fab
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