← previous blocknext block →recent activity
Analyzing
Block #91,424,641
24 transactions · 23 stateful · 2026-07-29 19:16:16 UTC
Parallelism
46/100
Blocked
70%
Avg conflicts / tx
3.58
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #91,424,641 · 24 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
1w02w13w25w38w210w011w112w213w314w415w516w617w718w819w920w1021w1122w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…004c
0x80c745…7210
26 touches
78 conflicts
0x00000000…004b
0x80c745…7210
26 touches
78 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xa38c430a…e3cb
0x34b655…2a6f
4 touches
1 conflict
0x08da804a…1992
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb2195a0c…68ca
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: 0x80c74517…647210
78 conflicts on slot 0x0000000000…00004c
Audit this contract →
← previous block·next block →recent activity